NASLite Network Attached Storage

Perform the operation on my nas and all is well.

Disk-3 had a total of 5.787 files and 321 folders and total data of 78GB.

I deleted both the lost and found folders on both HD's

Now going to delete the lot and see if i can get the error.
Note this was a second back up..

Mirror Details:

Initiate Mirror Event: Thu Dec 21 23:00:01 UTC 2006
Mirror Definition: 192.168.0.254/Disk-3/23
Source Host IP Address: 192.168.0.254
Source Volume Name: Disk-3
Source Target: Available
Initiate transport agent: rsync version 2.6.6 protocol version 29

Number of files: 6108
Number of files transferred: 47
Total file size: 78907484455 bytes
Total transferred file size: 4697385327 bytes
Literal data: 4697385327 bytes
Matched data: 0 bytes
File list size: 230411
File list generation time: 5.328 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 1169
Total bytes received: 4698191380

sent 1169 bytes received 4698191380 bytes 10498754.30 bytes/sec
total size is 78907484455 speedup is 16.80
Close transport agent: Code (0)
Close Mirror Event: Thu Dec 21 23:07:28 UTC 2006

Well, the problem is the same in three instances (Three drives mirrored from "NAS01" to "NAS02").

I will see to monitoring the memory usage next time.

t_indra,

I am trying to reproduce the error and for me its working fine every time.
I thought it could be the lost found folder, but I have managed to mirror with that folder there.

What are the specs of the servers.

would you be able to throw in a small HD in the source NAS and only have a handful of files there and then try the back up. the dest being clear of files.

After many hours of testing I cant get the same error as you. at first I thought it could be zero byte files,

I think there maybe a problem with either some files or folders? on your machine. what Rsync is doing is its hit a problem and rather then delete the files on the Dest is think better to leave them and hence skips them.
this is to safeguard your data. it would be nice for other members to try this feature and post back their results.

I've beaten this thing to death the last couple of days and have had absolutely no problems, so at this point I think it's best to assume that the problem needs to be identified before we proceed.

The v2.04 release will include a number of enhancements to the mirror in order to allow intelligent analysis of such problems. Since the rsync logs can get VERY large, a mirror-specific rsync log will be placed in the root of the mirror drive. That is possible to do with the latest release of rsync - v2.6.9, so the binary will be updated. The file will be named MIRROR.LOG and will contain a complete account of the mirror event including error details.

Implementing a mirror alarm will also alert of mirror failure so the issue can be addressed in a timely manner.

At this point Thorsten, it's probably best to continue with your original strategy until v2.04 is out. At that time you'll be able to review the log and handle the problem accordingly.

----------
P.S.

Is anyone else using the mirror? Any comments?

Hello Gaiden, thanks for your help efforts, but the problems had been persistent in my case.
What I have worked out with Tony in the meantime is that the culprit in my setup was the presence of the lost+found folders. A temporary workaround for now was to delete them, then things are working VERY fast and smooth.