On Sat, 30 Jul 2005, Archaic wrote: > On Fri, Jul 29, 2005 at 09:48:17PM +0100, Ken Moffat wrote: > > I've got one box chugging away as my main server, serving all my local > > tarballs over nfs to my other boxes. I've also got another box, to > > eventually become my new server (needs a cable so I can test my tape > > drive with 2,6 kernels, and needs me to get my pure64 build working > > reliable), on which I make backups with rsync to an nfs mount. > > If rsync is touching all the backups at some point, then I would point > to that. I have had it mangle many tarballs and stopped using it because > of that. > >
Thanks for that interesting comment. I can see it could happen to all of the backups (first I rsync to the other machine, then I roll down a series of backups and rsync the "staging" copy to the newest of the series). But surely rsync wouldn't alter the original tarball ? How long ago did you give up on rsync ? Meanwhile, yesterday was the day I did some more backing up to tape. The first filesystem is pre-tarred by a cron job, after that it's a matter of judgement what else I write to tape. I just write a series of uncompressed tarballs, created from tarring up filesystems. Now that I've got copies of everything on the second server, it was easiest to create the tarballs there. Then I mounted them over nfs and copied them to the old server ready to write to tape from the staging directory. After the problems, I decided it was best to take md5sums after copying : two differed (out of about 10 copied). Repeated, this time copying with scp : one of the two was ok, but the other had to be copied twice before I got the correct md5. This is reminiscent of my .sig (the first tiem as tragedy, the second as farce) - this is definitely reaching the farce stage for me. Earlier this year I was trying to get 2.6 kernels ported to the AmigaOne. One of the big problems was a lack of cache-coherency. By throttling the ide dma in kernels up to 2.6.9 I eventually got it to work for me (then 2.6.10 broke this, and shortly afterwards that system died from overheating). But that was a chipset that was known to be crap. My old server is a two or three year old pentiumIII running 2.4 (and the new is an athlon64 running 2.6.11.9 as i686) and these should just work :) Ken -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-chat FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
