From: Ulli Horlacher <framstag@rus.uni-stuttgart.de>
To: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: subvolume list as user?
Date: Sat, 16 Sep 2017 16:37:02 +0200 [thread overview]
Message-ID: <20170916143702.GO32347@rus.uni-stuttgart.de> (raw)
In-Reply-To: <684fb723-4270-9589-b80b-e60ccc6dadfe@mendix.com>
On Sat 2017-09-16 (14:39), Hans van Kranenburg wrote:
> On 09/16/2017 11:45 AM, Ulli Horlacher wrote:
>
> > Every user can create subvolumes (and root cannot prevent it!).
> > But how can a user list these subvolumes?
> >
> > tux@xerus:/test/tux: btrfs subvolume create test
> > Create subvolume './test'
>
> From your other posts I don't quickly get if you actually do want to
> have this possible, or accept that it's currently like that and try to
> do damage control by having users also remove their things again.
I want both, country AND western :-)
Without joking:
I just want to learn more about btrfs and I have various use cases to
handle.
Different use cases need different actions.
> Actually, if you don't want this I think it's quite easily to patch your
> kernel with one or two lines of code to disallow it.
Kernel patching is a no-go for me. My boss does not allow it. No
discussion possible on this topic.
> > tux@xerus:/test/tux: btrfs subvolume list .
> > ERROR: can't perform the search - Operation not permitted
>
> Yes, because the SEARCH ioctl only allows root to directly query any of
> the filesystem metadata from kernel memory. subvolume list uses this
> SEARCH ioctl to find it's info.
This is the explantion why it does not work, but it does not help me. I
still have the problem: how can a user get a list of his subvolumes? He
may created them some time ago and forget it. He now wants to have a list
of them.
--
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:<684fb723-4270-9589-b80b-e60ccc6dadfe@mendix.com>
next prev parent reply other threads:[~2017-09-16 14:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-16 9:45 subvolume list as user? Ulli Horlacher
2017-09-16 12:39 ` Hans van Kranenburg
2017-09-16 13:40 ` Hans van Kranenburg
2017-09-16 14:37 ` Ulli Horlacher [this message]
2017-09-16 20:56 ` Goffredo Baroncelli
2017-09-17 8:48 ` Ulli Horlacher
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=20170916143702.GO32347@rus.uni-stuttgart.de \
--to=framstag@rus.uni-stuttgart.de \
--cc=hans.van.kranenburg@mendix.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