From: Kai Krakow <hurikhan77@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: A user cannot remove his readonly snapshots?!
Date: Sat, 16 Sep 2017 01:22:48 +0200 [thread overview]
Message-ID: <20170916012248.0870f72d@jupiter.sol.kaishome.de> (raw)
In-Reply-To: 20170915220201.GH32347@rus.uni-stuttgart.de
Am Sat, 16 Sep 2017 00:02:01 +0200
schrieb Ulli Horlacher <framstag@rus.uni-stuttgart.de>:
> On Fri 2017-09-15 (23:44), Ulli Horlacher wrote:
> > On Fri 2017-09-15 (22:07), Peter Grandi wrote:
> >
> [...]
> > >
> > > Ordinary permissions still apply both to 'create' and 'delete':
> >
> > My user tux is the owner of the snapshot directory, because he has
> > created it!
>
> I can delete normal subvolumes but not the readonly snapshots:
>
> tux@xerus:/test/tux/zz/.snapshot: btrfs subvolume create test
> Create subvolume './test'
>
> tux@xerus:/test/tux/zz/.snapshot: ll
> drwxr-xr-x tux users - 2017-09-15 18:22:26
> 2017-09-15_1822.test drwxr-xr-x tux users - 2017-09-15
> 18:22:26 2017-09-15_1824.test drwxr-xr-x tux users -
> 2017-09-15 18:57:39 2017-09-15_1859.test drwxr-xr-x tux
> users - 2017-09-15 23:58:51 test
>
> tux@xerus:/test/tux/zz/.snapshot: btrfs subvolume delete test
> Delete subvolume (no-commit): '/test/tux/zz/.snapshot/test'
>
> 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. But this is said to has
security implication I cannot currently tell. Maybe someone else knows.
--
Regards,
Kai
Replies to list-only preferred.
next prev parent reply other threads:[~2017-09-15 23:22 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 [this message]
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=20170916012248.0870f72d@jupiter.sol.kaishome.de \
--to=hurikhan77@gmail.com \
--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).