On 2017-09-15 15:32, Ulli Horlacher wrote:
On Fri 2017-09-15 (13:08), Austin S. Hemmelgarn wrote:
On 2017-09-15 12:37, Ulli Horlacher wrote:
I have my btrfs filesystem mounted with option user_subvol_rm_allowed
tux@xerus: btrfs subvolume delete /test/tux/zz/.snapshot/2017-09-15_1824.test
Delete subvolume (no-commit): '/test/tux/zz/.snapshot/2017-09-15_1824.test'
ERROR: cannot delete '/test/tux/zz/.snapshot/2017-09-15_1824.test': Read-only
file system
root can delete this snapshot, but not the user. Why?
Add 'user_subvol_rm' to the mount options and try again.
root@xerus:~# mount -vo user_subvol_rm /dev/sdd4 /test
mount: wrong fs type, bad option, bad superblock on /dev/sdd4,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
root@xerus:~# dmesg | tail -2
[1514588.018991] BTRFS info (device sdd4): unrecognized mount option
'user_subvol_rm'
[1514588.028430] BTRFS: open_ctree failed
user_subvol_rm is not listed on
https://btrfs.wiki.kernel.org/index.php/Mount_options
Did you mean user_subvol_rm_allowed?
Yes, that's what I meant, sorry about the confusion.
I have already used this option, without success. See above.
I missed that, sorry.
--
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
