DJA wrote:
Update your rsync on *both* machines. Make sure the version numbers
are very close (identical ideally).
Not required. You're just copying on the same machine.
I guess that begs the definition of "cheap". I have tried both a Netgear
FVS-318v3 and Linksys RV082 router/firewalls. If you mean "Consumer
grade", then yeah, cheap.
Dunno. But just something to think about.
Unfortunately, as explained above, SCP is not yet an option. I do have
the options of using either FTP or HTTP(S), but I want to work on one
problem at a time (NFS), and anyway I'm not too keen on using those
protocols at the present.
NFS ... I can go on and on ...
However, the good news is that you can probably use tar.
Use 'tar cvf /some/big/partition/tarfile.name.tgz .' from inside the
directory to pack it up. If there is a read error going on, tar will
flush it out and you won't have to get NFS involved at all.
/some/big/partition should be on a local drive rather than NFS.
That '.' is kinda important. It creates a relative tar.
You could also use, './<mydirectory>', but then that will recreate the
toplevel directory, too.
After creating the tarfile, you can change to the NFS mounted directory
and unpack using 'tar xvf /some/big/partition/tarfile.name.tgz' and
extract it all. At this point, if there is a write error, the fault is
NFS/Ethernet rather than filesystem/fileit.
That should break the problem apart for you.
-a
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
