I'm investigating using btrfs for archiving old data and offsite storage, essentially put 2 drives in btrfs RAID-1, copy the data to the filesystem and then unmount, remove a drive and take it to an offsite location. Remount the other drive -o ro,degraded until my systems slots fill up, then remove the local drive and put it on a shelf. I'd verify the file md5sums after data is written to the drive for piece of mind, but maybe a btrfs scrub would give the same assurances. Seem straightforward? Anything to look out for? Long term format stability seems good, right? Also, I like the idea of being able to pull the offsite drive back and scrub if the local drive ever has problems, a nice extra piece of mind we wouldn't get with ext4. Currently using the 4.1.32 kernel since the driver for the r750 card in our 45 drives system only supports up to 4.3 ATM. -- 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
