From: Ulli Horlacher <framstag@rus.uni-stuttgart.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: A user cannot remove his readonly snapshots?!
Date: Fri, 15 Sep 2017 21:32:11 +0200 [thread overview]
Message-ID: <20170915193211.GE32347@rus.uni-stuttgart.de> (raw)
In-Reply-To: <38b35e41-313a-1eed-667a-ee3138c8170d@gmail.com>
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?
I have already used this option, without success. See above.
--
Ullrich Horlacher Server und Virtualisierung
Rechenzentrum TIK
Universitaet Stuttgart E-Mail: horlacher@tik.uni-stuttgart.de
Allmandring 30a Tel: ++49-711-68565868
70569 Stuttgart (Germany) WWW: http://www.tik.uni-stuttgart.de/
REF:<38b35e41-313a-1eed-667a-ee3138c8170d@gmail.com>
next prev parent reply other threads:[~2017-09-15 19:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 16:37 A user cannot remove his readonly snapshots?! Ulli Horlacher
2017-09-15 17:08 ` Austin S. Hemmelgarn
2017-09-15 19:32 ` Ulli Horlacher [this message]
2017-09-18 11:36 ` Austin S. Hemmelgarn
2017-09-15 21:07 ` Peter Grandi
2017-09-15 21:44 ` Ulli Horlacher
2017-09-15 22:02 ` Ulli Horlacher
2017-09-15 23:22 ` Kai Krakow
2017-09-16 7:36 ` Ulli Horlacher
2017-09-16 11:29 ` Kai Krakow
2017-09-16 9:04 ` Goffredo Baroncelli
2017-09-16 9:22 ` Ulli Horlacher
2017-09-16 9:16 ` Peter Grandi
2017-09-16 8:10 ` Goffredo Baroncelli
2017-09-16 8:54 ` Ulli Horlacher
2017-09-16 10:19 ` Ulli Horlacher
2017-09-16 10:43 ` Marat Khalili
2017-09-16 11:47 ` Kai Krakow
2017-09-16 14:28 ` Ulli Horlacher
2017-09-18 11:39 ` Austin S. Hemmelgarn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170915193211.GE32347@rus.uni-stuttgart.de \
--to=framstag@rus.uni-stuttgart.de \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).