[lug] NSLU2 as backup device

[Lee Woodworth]

bgiles at coyotesong.com wrote:
>> bgiles at coyotesong.com wrote:
>> [...]
>>> The next most likely culprit is probably computing the hashes... unless
>>> that's cached somewhere.
>> Yes, on a fast network rsync can be relatively slow because hashing
>> makes it CPU bound.  You can turn that off and transfer entire files.
> 
> It's on a 100MB wired network but only 133MHz and 32M of memory.
How many files? rsync makes a list of all the files it is going
to transfer in memory. With only 32M you may be swapping.

> 
> Hmmm, even an idle system (running 'top', admittedly) has a load average
> around 2.5.   Ah...., it's running 'updatedb' in the background.  That's
> entirely local and should have finished hours ago....
> 
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: lug.boulder.co.us port=6667 channel=#colug