> Ok, latest kernels include this commit: > > commit 72de6b5393c15c5228074008bbdc47e92bf6d4f7 > Author: Guangyu Sun <[email protected]> > Date: Tue Mar 11 11:24:18 2014 -0700 > > Btrfs: return EPERM when deleting a default subvolume > > The error message is confusing: > > # btrfs sub delete /mnt/mysub/ > Delete subvolume '/mnt/mysub' > ERROR: cannot delete '/mnt/mysub' - Directory not empty > > The error message does not make sense to me: It's not about deleting a > directory but it's a subvolume, and it doesn't matter if the subvolume is > empty or not. > > Maybe EPERM or is more appropriate in this case, combined with an > explanatory > kernel log message. (e.g. "subvolume with ID 123 cannot be deleted because > it is configured as default subvolume.") > > Reported-by: Koen De Wit <[email protected]> > Signed-off-by: Guangyu Sun <[email protected]> > Reviewed-by: David Sterba <[email protected]> > Signed-off-by: Chris Mason <[email protected]> > > And your btrfs-debug-tree output confirms you're trying to delete the > default subvolume. > > Pick a new default and it will all work ;)
yep, and that was (embarrassingly) it. set the default to 5, so i can remove my use of subvolumes altogether and redo them properly. and the delete of course succeeds now. thanks -- Shaun Reich, KDE Software Developer (kde.org) -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
