2014-12-01 14:12 GMT+01:00 Austin S Hemmelgarn <ahferroin7@xxxxxxxxx>: > > We might want to consider adding an option to btrfs subvol del to ask for > confirmation (or make it do so by default and add an option to disable > asking for confirmation). > I've also noticed, a subvolume can just be deleted with an "rm -r", just like an ordinary directory. I'd consider to only allow subvolume deletions with exact "btrfs subvolume delete" commands, and they should be protected against an ordinary "rm". There also could be a tunable FS feature to allow or disable ordinary subvolume deletions, which could be set or unset by btrfstune. I think a subvolume really deserves to be treated specially over an ordinary directory. As for undeletion, while I have no idea how to do that, I noticed they don't get deleted immediately. With older btrfs tools (3.12), I noticed, if I delete a subvolume and then immediately issue a "btrfs subvolume list", my deleted subvolume is still listed with a "DELETED" caption, and allocated space doesn't immediately gets freed if I check with "df -m". It takes a few seconds for the DELETED entry to disappear and the allocated space to be freed. -- 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
