linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Nikos Voutsinas" <nvoutsin@noc.edunet.gr>
To: dave@jikos.cz
Cc: linux-btrfs@vger.kernel.org
Subject: Re: subvolume info in /proc/mounts
Date: Sun, 5 Feb 2012 12:30:42 +0200	[thread overview]
Message-ID: <2ed5fe028fdcfd3d53cf217e13b827d9.squirrel@webmail01.edunet.gr> (raw)
In-Reply-To: <20120204214430.GA15350@twin.jikos.cz>

> Hi,
>
> On Sat, Feb 04, 2012 at 08:40:51PM +0200, Nikos Voutsinas wrote:
>> There was a patch to include the subvolume mount option into
>> /proc/mounts.
>> Did that make it into the kernel;
>
> I havent' seen such patch, do you have a link?
>
>> If not, what is the formal way to find out which subvolume is mounted;
>
> Not right now, see detailed answer to a similar question:
> http://permalink.gmane.org/gmane.comp.file-systems.btrfs/15385
>
> In short, possible but not implemented.
>

It's quite old, but what was this about;

http://thread.gmane.org/gmane.comp.file-systems.btrfs/4487

Assuming that pools with multiple subvolumes and/or snapshots is the way
of doing things in btrfs, the subvolume info is required for the every day
administration.


  reply	other threads:[~2012-02-05 10:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-04 18:40 subvolume info in /proc/mounts Nikos Voutsinas
2012-02-04 21:44 ` David Sterba
2012-02-05 10:30   ` Nikos Voutsinas [this message]
2012-02-05 23:38     ` Fajar A. Nugraha
2012-02-06 11:53     ` David Sterba
2012-02-06 12:18       ` Christoph Hellwig
2012-02-06 13:52         ` Al Viro
2012-02-09 13:44           ` David Sterba
2012-02-21 14:31             ` David Sterba
2012-02-07 19:05         ` Goffredo Baroncelli
2012-02-06  9:52 ` Karel Zak
  -- strict thread matches above, loose matches on Subject: below --
2012-02-10 22:42 Nikos Voutsinas

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=2ed5fe028fdcfd3d53cf217e13b827d9.squirrel@webmail01.edunet.gr \
    --to=nvoutsin@noc.edunet.gr \
    --cc=dave@jikos.cz \
    --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).