From: Omar Sandoval <osandov@osandov.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: bug: proc mountinfo, findmnt, and subvol vs subvolid
Date: Thu, 9 Apr 2015 12:41:18 -0700 [thread overview]
Message-ID: <20150409194118.GB12447@mew> (raw)
In-Reply-To: <CAJCQCtRnS_s2MxpvmrPv9_-Rn6-kfJ0wLxhgbDKoO0DtWi9Uig@mail.gmail.com>
On Thu, Apr 09, 2015 at 01:38:19PM -0600, Chris Murphy wrote:
> Another way to put this is, the only reliable way to mount and get
> subvolume info in findmnt and /proc is by using subvol=.
>
> When using subvolid=, the subvolume info isn't available unless the
> initial mount is the top level (ID 5).
Working on it :) https://lkml.org/lkml/2015/4/8/16
--
Omar
next prev parent reply other threads:[~2015-04-09 19:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 19:32 bug: proc mountinfo, findmnt, and subvol vs subvolid Chris Murphy
2015-04-09 19:38 ` Chris Murphy
2015-04-09 19:41 ` Omar Sandoval [this message]
2015-04-09 19:53 ` Chris Murphy
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=20150409194118.GB12447@mew \
--to=osandov@osandov.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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