On Mon, 20 Apr 2020 12:05:58 +0200 Nick Gilmour <nickeforos@xxxxxxxxx> wrote: > # btrfs subvolume delete /tlsv5/@.broken.20190830a > > Delete subvolume (no-commit): '/tlsv5/@.broken.20190830a' > ERROR: Could not destroy subvolume/snapshot: Directory not empty It appears like it contains a few other subvolumes: > ID 324 gen 54829 top level 257 path > <FS_TREE>/@.broken.20190830a/var/lib/portables > ID 351 gen 268851 top level 257 path > <FS_TREE>/@.broken.20190830a/var/lib/docker/btrfs/subvolumes/641bd5ec86e1c5e1f2d504a0656da736bafb858551067aca7f1b84c24c1e7d33 > ... Even though it doesn't really "contain" them for the purposes of snapshotting, for deletion you first have to remove all the nested ones. I believe in recent enough kernels the regular "rmdir" call is able to remove empty subvolumes, so doing an "rm -rf" on the subvolume you want to remove will take care of all the nested ones (if any). Or if there's just a couple, then just remove them manually first. -- With respect, Roman
