NASLite Network Attached Storage

i have 2 naslite 2.04 servers i get the following report when the mirror has finished..

Initiate Mirror Event: Wed Feb 21 13:00:01 UTC 2007
Mirror Definition: 192.168.22.123/Disk-1/13
Source Host IP Address: 192.168.22.123
Source Volume Name: Disk-1
Source Target: Available
Initiate transport agent: rsync version 2.6.9 protocol version 29

Number of files: 9978
Number of files transferred: 0
Total file size: 32374144893 bytes
Total transferred file size: 0 bytes
Literal data: 0 bytes
Matched data: 0 bytes
File list size: 187555
Total bytes sent: 114
Total bytes received: 187591

sent 114 bytes received 187591 bytes 1345.56 bytes/sec
total size is 32374144893 speedup is 172473.54
Close transport agent: Code (23)
Mirror Details Log: MIRROR LOG
Close Mirror Event: Wed Feb 21 13:02:21 UTC 2007

the mirror log consists of a lot of lines like this:-

2007/02/21 13:00:13 [28019] receiving file list
2007/02/21 13:02:20 [28019] rsync: chown "/export/Disk-0/." failed: Invalid argument (22)
2007/02/21 13:02:20 [28019] rsync: chown "/export/Disk-0/6th October 22003.doc" failed: Invalid argument (22)
2007/02/21 13:02:20 [28019] rsync: chown "/export/Disk-0/AdobeStockPhotos" failed: Invalid argument (22)
2007/02/21 13:02:20 [28019] rsync: chown "/export/Disk-0/AdobeStockPhotos/Downloaded Comps" failed: Invalid argument (22)
etc.

any idea what is causing this??

How were the files written to the drives?

Good evening tony,

your question may me the clue to the solution....

i have the two naslite boxes at different sites connected via vpn.

so i didnt have to push 30+GB down the vpn i copied the files onto a spare hard disk at site 1

then connected it to a computer at site2
I then copied the files onto the desination mirror drive using ftp to the nas lite box (as i find ftp the fastest).

the idea was to 'seed' the mirror to reduce the initial sync time.

however, by your reply this may be the source of my problem...

The problem is definitely caused by improperly set permissions. Make sure that all NASLite hosted files that you wrote on the drives via alternate methods are GID/UID 98/98 and set the permissions to 777. That will allow rsync the proper access to manipulate the content.

Hope that helps.

thanks for the prompt reply tony,

ive setup an rsync server on my windows box,
Ive formatted the naslite2 drive with naslite2 and i'm currently starting a local mirror initiated from the naslite2 box to mirror the share on the windows box.

i will see if:-

a) this mirror completes cleanly (which will prove that it is possible to mirror a folder declared by rsync on a WXP machine.)

b) this can then be reconfigured so the mirror points to my second naslite box via the vpn...

i will keep ths thread updated with the results.

PS ...the concept is:-

my sister in law is a photographer, one naslite box is at her house, this will mirror her 'my documents' directory (containing all her photos etc.)

The second naslite box is at my house and will mirror the first box as a type of offsite backup.