Linux-BTRFS Archive on lore.kernel.org
 help / color / Atom feed
From: Ulli Horlacher <framstag@rus.uni-stuttgart.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: find subvolume directories
Date: Sat, 13 Jul 2019 13:28:32 +0200
Message-ID: <20190713112832.GA30696@tik.uni-stuttgart.de> (raw)
In-Reply-To: <62366a29-a8ea-a889-f857-0305eba99051@gmail.com>

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?


-- 
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:<62366a29-a8ea-a889-f857-0305eba99051@gmail.com>

  reply index

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12 23:17 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 [this message]
2019-07-13 15:08         ` Andrei Borzenkov
2019-07-15 13:22         ` Piotr Szymaniak
2019-07-15 11:39       ` Ulli Horlacher
2019-07-15 11:33 ` Ulli Horlacher

Reply instructions:

You may reply publically 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=20190713112832.GA30696@tik.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

Linux-BTRFS Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-btrfs/0 linux-btrfs/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-btrfs linux-btrfs/ https://lore.kernel.org/linux-btrfs \
		linux-btrfs@vger.kernel.org linux-btrfs@archiver.kernel.org
	public-inbox-index linux-btrfs


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-btrfs


AGPL code for this site: git clone https://public-inbox.org/ public-inbox