On Sat, Mar 22, 2014 at 09:44:05PM +0200, Brendan Hide wrote: > Hi, Marc > > Feel free to use ideas from my own script. Some aspects in my script are > more mature and others are frankly pathetic. ;) > > There are also quite a lot of TODOs throughout my script that aren't > likely to get the urgent attention they deserve. It has been slowly > evolving over the last two weeks. > > http://swiftspirit.co.za/scripts/btrfs-snd-rcv-backup I figured I likely wasn't the only one working on a script like this :) >From a quick read, it looks even more complex than mine :) but - it doesn't do ssh to a destination for a remote backup - it doesn't seem to keep a list of configurable snapshots not necessary for send/restore but useful for getting historical data - it doesn't seem to use a symlink to keep track of the last complete snapshot on the source and destination, and does more work to compensate when recovering from an incomplete backup/restore. - it doesn't create writeable snapshots on the destination in case you want to use the copy as a live filesystem Things I noticed: - I don't use ionice, maybe I should. Did you find that it actually made a difference with send/receive? - Your comments say shlock isn't safe and that's documented. I don't see that in the man page http://manpages.ubuntu.com/manpages/trusty/man1/shlock.1.html I'd love to have details on this if I shouldn't be using it - Is set -o noclobber; echo $$ > $lockfile really atomic and safer than shlock? If so, great, although I would then wonder why shlock even exists :) Thanks, Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
