From: Ulli Horlacher <framstag@rus.uni-stuttgart.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: A user cannot remove his readonly snapshots?!
Date: Sat, 16 Sep 2017 09:36:33 +0200 [thread overview]
Message-ID: <20170916073633.GI32347@rus.uni-stuttgart.de> (raw)
In-Reply-To: <20170916012248.0870f72d@jupiter.sol.kaishome.de>
On Sat 2017-09-16 (01:22), Kai Krakow wrote:
> > tux@xerus:/test/tux/zz/.snapshot: btrfs subvolume delete
> > 2017-09-15_1859.test Delete subvolume (no-commit):
> > '/test/tux/zz/.snapshot/2017-09-15_1859.test' ERROR: cannot delete
> > '/test/tux/zz/.snapshot/2017-09-15_1859.test': Read-only file system
>
> See "man mount" in section btrfs mount options: There is a mount option
> to allow normal user to delete snapshots.
As I wrote first: "I have mounted with option user_subvol_rm_allowed"
tux@xerus:/test/tux/zz/.snapshot: mount | grep /test
/dev/sdd4 on /test type btrfs (rw,relatime,space_cache,user_subvol_rm_allowed,subvolid=5,subvol=/)
This does not help. A user cannot remove a readonly snapshot he just has
created.
--
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:<20170916012248.0870f72d@jupiter.sol.kaishome.de>
next prev parent reply other threads:[~2017-09-16 7:36 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
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 [this message]
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=20170916073633.GI32347@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).