All of lore.kernel.org
 help / color / mirror / Atom feed
* bug: proc mountinfo, findmnt, and subvol vs subvolid
@ 2015-04-09 19:32 Chris Murphy
  2015-04-09 19:38 ` Chris Murphy
  0 siblings, 1 reply; 4+ messages in thread
From: Chris Murphy @ 2015-04-09 19:32 UTC (permalink / raw)
  To: Btrfs BTRFS

kernel-4.0.0-0.rc6.git0.1.fc22.i686


The short version is that if the top level subvolume is not mounted
first, any usage of subvolid= fails to show the subvolume in either
findmnt or /proc/self/mountinfo.

That is, only when the initial mount is the top level, any subsequent
mount using option subvolid= or subvol= will show the subvolume name
in findmnt and /proc/self/mountinfo.

This seems like a bug.

-- 
Chris Murphy

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: bug: proc mountinfo, findmnt, and subvol vs subvolid
  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
  0 siblings, 1 reply; 4+ messages in thread
From: Chris Murphy @ 2015-04-09 19:38 UTC (permalink / raw)
  To: Chris Murphy; +Cc: Btrfs BTRFS

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).


-- 
Chris Murphy

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: bug: proc mountinfo, findmnt, and subvol vs subvolid
  2015-04-09 19:38 ` Chris Murphy
@ 2015-04-09 19:41   ` Omar Sandoval
  2015-04-09 19:53     ` Chris Murphy
  0 siblings, 1 reply; 4+ messages in thread
From: Omar Sandoval @ 2015-04-09 19:41 UTC (permalink / raw)
  To: Chris Murphy; +Cc: Btrfs BTRFS

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: bug: proc mountinfo, findmnt, and subvol vs subvolid
  2015-04-09 19:41   ` Omar Sandoval
@ 2015-04-09 19:53     ` Chris Murphy
  0 siblings, 0 replies; 4+ messages in thread
From: Chris Murphy @ 2015-04-09 19:53 UTC (permalink / raw)
  To: Omar Sandoval; +Cc: Chris Murphy, Btrfs BTRFS

On Thu, Apr 9, 2015 at 1:41 PM, Omar Sandoval <osandov@osandov.com> wrote:
> 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

OK great. Seems like it could also (passively) relate to the
"mlocate/updatedb and btrfs subvolume mounts" thread.


-- 
Chris Murphy

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2015-04-09 19:53 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2015-04-09 19:53     ` Chris Murphy

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.