Mark Lanctot wrote: > It seemed to work - there was an identical number of files and the data > size was identical. However my File Browser window gave a rather > alarming description - -some of the contents could not be read-.
You dont say which "File Browser window". Could this be a permissions problem? If there was a problem reading the disk image then there will be an entry in syslog. > I'm investigating rsync and I'm currently carrying out: > > rsync -t -r [source] [dest] That looks fine. You may also want -P, to see a progress display during the copy. > but this is taking so long it must be > copying every file and folder. > > What's going on? Is it still running, right now? If you want to see what's going without interrupting on you can use 'strace': Find the pid of your rsync process using 'top' or 'ps' (or whatever). Then run 'strace -e file -p 12345' (replace 12345 with the pid). You should see some filename filenames scrolling past as rsync accesses them. Press Ctrl+C when you have seen enough. I think you should have two rsync process - one for reading and one for writing. > Are all my files corrupted? Is rsync doing something > stupid like make a duplicate of every file? Ive had problems with rsync with trailing slashes at the end of directory names, then rsync creating a duplicate directory inside the old backup directory. > Once rsync is finished, how > can I independently verify that every single file transferred over > without any errors? MD5 sums? Yes, if you are worried that the bytes might not have been transferred. If you are worried that you might have missed some files due to pilot error then a diff of directory listings will be quicker. [fwiw Im not using rsync for my music backups any more. Incremental backups using rsnapshot are much safer] _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/unix
