On Thu, Jul 7, 2016 at 10:01 AM, Henk Slager <eye...@gmail.com> wrote:
> What the latest debian likes as naming convention I dont know, but in > openSuSE @ is a directory in the toplevel volume (ID=5 or ID=0 as > alias) and that directory contains subvolumes. No, opensuse doesn't use @ at all. They use a subvolume called .snapshots to contain snapper snapshots. On a system using snapper, its snapshots should probably be deleted via snapper so it's aware of the state change. And very clearly from the OP's output from 'btrfs sub list' there are no subvolumes with @ in the path, so there is no subvolume @, nor are there any subvolumes contained in a directory @. Assuming the posted output from btrfs sub list is the complete output, .snapshots is a directory and there are three subvolumes in it. I suspect the OP is unfamiliar with snapper conventions and is trying to delete a snapshot outside of snapper, and is used to some other (Debian or Ubuntu) convention where snapshots somehow relate to @, which is a mimicking of how ZFS does things. Anyway the reason why the command fails is stated in the error message. The system appears to be installed in the top level of the file system (subvolid=5), and that can't be deleted. First it's the immutable first subvolume of a Btrfs file system, and second it's populated with other subvolumes which would inhibit its removal even if it weren't the top level subvolume. What can be done is delete the directories in the top level, retaining the subvolumes that are there. -- Chris Murphy -- 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
