From: Andrei Borzenkov <arvidjaar@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: find subvolume directories
Date: Sat, 13 Jul 2019 18:08:29 +0300 [thread overview]
Message-ID: <5c596c6b-94cc-998b-6992-adcd15128178@gmail.com> (raw)
In-Reply-To: <20190713112832.GA30696@tik.uni-stuttgart.de>
13.07.2019 14:28, Ulli Horlacher пишет:
> On Sat 2019-07-13 (14:10), Andrei Borzenkov wrote:
>
>>>> It is entirely up to the user who creates it how subvolumes are named and
>>>> structured. You can well have /foo, /bar, /baz mounted as /, /var and
>>>> /home.
>>>
>>> And how can I find them in my mounted filesystem?
>>> THIS is my problem.
>>
>> I am not sure what problem you are trying to solve
>
> I want a list of all subvolumes directories (which I can access with UNIX
> tools like cd and ls or btrfs subvolume ...).
>
>
>> but you can use list of current mounts to build path to each subvolume
>> (as long as it is either below one of mounted subvolumes or explicitly
>> mounted).
>
> Is there an easy/standard way to do this?
>
>
Not that I'm aware of.
next prev parent reply other threads:[~2019-07-13 15:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 23:17 find subvolume directories Ulli Horlacher
2019-07-13 3:59 ` Andrei Borzenkov
2019-07-13 8:27 ` Ulli Horlacher
2019-07-13 11:10 ` Andrei Borzenkov
2019-07-13 11:28 ` Ulli Horlacher
2019-07-13 15:08 ` Andrei Borzenkov [this message]
2019-07-15 13:22 ` Piotr Szymaniak
2019-07-15 22:40 ` Ulli Horlacher
2019-07-15 23:58 ` [RFC] a standard user-friendly way to find a snapshot in nested subvolumes [was: find subvolume directories] Nicholas D Steeves
2019-07-16 0:41 ` Ulli Horlacher
2019-07-15 11:39 ` find subvolume directories Ulli Horlacher
2019-07-15 11:33 ` Ulli Horlacher
2019-07-16 11:04 ` Ulli Horlacher
2019-07-18 12:00 ` Axel Burri
2019-07-18 17:48 ` Andrei Borzenkov
2019-07-22 12:36 ` Axel Burri
2019-07-20 9:27 ` 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=5c596c6b-94cc-998b-6992-adcd15128178@gmail.com \
--to=arvidjaar@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).