On Dec 13, 2013, at 1:35 PM, Hugo Mills <[email protected]> wrote: > On Fri, Dec 13, 2013 at 07:44:16PM +0000, Martin wrote: >> OK... So for backing up across a local network to a second physical host... >> >> Is btrfs-send-receive stable enough now to be used? > > It seems to be OK for me at the moment -- I'm not running it across > a network (yet), but I am using it between different filesystems on > the same host, using pipes.
Question. Are the source file system's checksums (and metadata) preserved in the send file? Or does the send file just contain data, and checksums are recomputed on receive? I'm curious if the send file can be stored on a non-checksumming file system, and yet have a means to verify the integrity of the files once received. Either the checksums in the send file being check during receive, or subsequent to receive completion by using scrub? And yes I can confirm that send outputting to a file on a 2nd drive, and receiving it to yet another drive does work, and the source and destination subvolumes are the same in seemingly every way. I didn't separately rsync checksum compare the two subvolumes, however. That seems like possibly a good test. I also haven't tried doing it over a network. Chris Murphy-- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
