To support the Gentoo Linux ecosystem I do maintain a server as a tinderbox. I create chroot images based on various Gentoo minmal ISO images. I usually run 4 chroot image jobs in parallel. The chroots are full-filled over days/weeks with the compiled output. Issues during that are filed into Gentoo's bugzilla. If an image is "full" (~35 GB with many files + directories in it) or completely bricked I create a new one of the same type. The old is kept for weeks/months to further serve to bug reports questions. But old images are rarely accessed usually. Because deleting a chroot image takes awfully long and b/c I experience iowait spikes even if the 3 TB drive isn't filled by more than 50% I do wonder, if it would make sense to create a btrfs subvolume for each chroot image ? The deletion of a subvolume should be fast compared to recursivly deleting a 35 GB file system structure, right ? (And BTW what's about re-balancing of the BTRFS-tree during the daily usage: wouldn't this profit from that too ? -- Toralf pgp key: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 0076 E94E -- "; the past is all dirty and cruel in the modern popular imagination, with the exception of the Romans, who are just cruel" Ian Mortimer, 2008, "The Time Traveller's Guide to Medieval England" -- 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
