linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Calvin Walton <calvin.walton@kepstin.ca>, linux-btrfs@vger.kernel.org
Subject: Re: Subvolumes and /proc/self/mountinfo
Date: Wed, 20 Jun 2012 09:21:36 +0100	[thread overview]
Message-ID: <20120620082136.GA25572@carfax.org.uk> (raw)
In-Reply-To: <4FE10CDF.5050102@zytor.com>

[-- Attachment #1: Type: text/plain, Size: 1397 bytes --]

On Tue, Jun 19, 2012 at 04:35:59PM -0700, H. Peter Anvin wrote:
> On 06/19/2012 07:22 AM, Calvin Walton wrote:
> > 
> > All subvolumes are accessible from the volume mounted when you use -o
> > subvolid=0. (Note that 0 is not the real ID of the root volume, it's
> > just a shortcut for mounting it.)
> > 
> 
> Could you clarify this bit?  Specifically, what is the real ID of the
> root volume, then?
> 
> I found that after having set the default subvolume to something other
> than the root, and then mounting it without the -o subvol= option, then
> the subvolume name does *not* show in /proc/self/mountinfo; the same
> happens if a subvolume is mounted by -o subvolid= rather than -o subvol=.
> 
> Is this a bug?  This would seem to give the worst of both worlds in
> terms of actually knowing what the underlying filesystem path would end
> up looking like.

   Yes, it's a bug, and rather an irritating one at that. I know that
David Sterba looked at fixing it, but apparently it was trickier to
fix than was expected. (I don't recall the reason, and probably
wouldn't have understood it anyway, so I'll leave it to Dave to tell
you about it in detail).

   Hugo.

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
               --- Doughnut furs ache me, Omar Dorlin. ---               

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

  parent reply	other threads:[~2012-06-20  8:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-19  0:39 Subvolumes and /proc/self/mountinfo H. Peter Anvin
2012-06-19 14:22 ` Calvin Walton
2012-06-19 23:35   ` H. Peter Anvin
2012-06-20  1:27     ` Fajar A. Nugraha
2012-06-20  8:21     ` Hugo Mills [this message]
2012-06-19 23:49 ` Chris Mason
2012-06-20  0:03   ` H. Peter Anvin
2012-06-20 13:34     ` Chris Mason
2012-06-20 15:59       ` H. Peter Anvin
2012-06-20  0:39   ` Helmut Hullen
2012-06-20  1:16     ` cwillu
2012-06-20  3:22       ` H. Peter Anvin
2012-06-20  6:31         ` Fajar A. Nugraha
2012-06-20 23:43           ` H. Peter Anvin

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=20120620082136.GA25572@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=calvin.walton@kepstin.ca \
    --cc=hpa@zytor.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).