This also occurs for limited user containers, without asking for a btrfs backing store. This is more of a problem as the limited user can't delete (or even detect) the subvolume themselves.
On a standard whole-partition-as-btrfs system, as setup by the installer, this looks like: ID 257 gen 46021 top level 5 path @ ID 258 gen 46021 top level 5 path @home ... ID 373 gen 35464 top level 257 path @/var/lib/machines ID 374 gen 45983 top level 258 path faux/.local/share/lxc/vivid/rootfs/var/lib/machines ID 395 gen 45995 top level 258 path faux/.local/share/lxc/vivid2/rootfs/var/lib/machines ID 396 gen 46011 top level 258 path faux/.local/share/lxc/vivid3/rootfs/var/lib/machines ID 397 gen 46014 top level 258 path faux/.local/share/lxc/vivid4/rootfs/var/lib/machines -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1441068 Title: lxc-destroy fails on btrfs subvolumes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1441068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
