On Wed, Mar 18, 2015 at 5:22 PM, K Richard Pixley <rpix...@graphitesystems.com> wrote: > Most of the uses I have for btrfs involve fairly dynamic use of snapshots, > typically by non-root users.
Another thing. Some distros behave this way: chris@linux-6gc0:~> btrfs sub list / Absolute path to 'btrfs' is '/usr/sbin/btrfs', so running it may require superuser privileges (eg. root). As is the case on openSUSE. On Fedora, any user can use the btrfs command, without sudo, and even without being in group wheel. Kindof a stark difference, I'm vaguely curious about the security implications. So this normal/non-admin user I'm logged in right now can create subvolumes and snapshots at will, but I can't delete them (as previously mentioned). Erkki's cp --reflink idea is a good one. I've often wondered if it's a good idea, and possible, to eventually make --reflink the default behavior with Btrfs copies (I think some things probably first need enhancement like the cross subvolume stuff, because otherwise cp could fail inexplicably). -- 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