Chris Murphy posted on Thu, 17 Sep 2015 12:35:41 -0600 as excerpted: > You'd use Btrfs snapshots to create a subvolume for doing backups of > the images, and then get rid of the Btrfs snapshot.
The caveat here is that if the VM/DB is active during the backups (btrfs send/receive or other), it'll still COW1 any writes during the existence of the btrfs snapshot. If the backup can be scheduled during VM/DB downtime or at least when activity is very low, the relatively short COW1 time should avoid serious fragmentation, but if not, even only relatively temporary snapshots are likely to trigger noticeable cow1 fragmentation issues eventually. Some users have ameliorated that by scheduling weekly or monthly btrfs defrag, reporting that cow1 issues with temporary snapshots build up slow enough that the scheduled defrag effectively eliminates the otherwise growing problem, but it's still an additional complication to have to configure and administer, longer term. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
