On Tue, Dec 2, 2014 at 8:44 AM, Zygo Blaxell <ce3g8...@umail.furryterror.org> wrote: > This is consistent with the > way lvm2 and mdadm work when presented with data-losing or otherwise > questionable commands and parameters. It will break scripts, but btrfs > users should still be expecting that for a while as undesirable default > behaviors are identified.
Ah so there *is* precedent for my hunch that deleting subvols should be different than deleting ordinary files and folders... :-) > OTOH maybe there is no issue with the current behavior. Only root can > delete subvolumes, and maybe we assume root knows what they're doing? Well in office environs, where the root password is with a certain person only, then that's fine because that person is going to be wary of doing anything that's make others angry at them, but on single-user systems, one's regular password *is* the root password and the situation is such that because ordinary (and mostly non-destructive) things like installing requires entering it, so one gets accustomed to entering it without too much thought, leading to the requirement for such safety nets. (Perhaps like in banks, we should have a two-password system, one for destructive actions, so the user is forced to apply thought to what they are approving!) > On a side note...only root can delete subvolumes, but non-root users > can create them, which results in...this: Not sure about your Debian system, but my openSUSE Tumbleweed (with kernel 3.17.2 and btrfsprogs 3.17) requires me to enter the root password before creating a subvol (or in fact running anything under /sbin or /usr/sbin). -- Shriramana Sharma ஶ்ரீரமணஶர்மா श्रीरमणशर्मा -- 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
