* what determines what /dev/ is mounted?
@ 2020-12-18 21:42 Chris Murphy
2020-12-19 6:51 ` Andrei Borzenkov
0 siblings, 1 reply; 2+ messages in thread
From: Chris Murphy @ 2020-12-18 21:42 UTC (permalink / raw)
To: Btrfs BTRFS
When I have a 2-device btrfs:
devid 1 = /dev/vdb1
devid 2 = /dev/vdc1
Regardless of the mount command, df and /proc/mounts shows /dev/vdb1 is mounted.
If I flip the backing assignments in qemu, such that:
devid 2 = /dev/vdb1
devid 1 = /dev/vdc1
Now, /dev/vdc1 is shown as mounted by df and /proc/mounts.
But this isn't scientific. Is there a predictable logic? Is it always
the lowest devid?
--
Chris Murphy
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: what determines what /dev/ is mounted?
2020-12-18 21:42 what determines what /dev/ is mounted? Chris Murphy
@ 2020-12-19 6:51 ` Andrei Borzenkov
0 siblings, 0 replies; 2+ messages in thread
From: Andrei Borzenkov @ 2020-12-19 6:51 UTC (permalink / raw)
To: Chris Murphy, Btrfs BTRFS
19.12.2020 00:42, Chris Murphy пишет:
> When I have a 2-device btrfs:
>
> devid 1 = /dev/vdb1
> devid 2 = /dev/vdc1
>
> Regardless of the mount command, df and /proc/mounts shows /dev/vdb1 is mounted.
>
> If I flip the backing assignments in qemu, such that:
>
> devid 2 = /dev/vdb1
> devid 1 = /dev/vdc1
>
> Now, /dev/vdc1 is shown as mounted by df and /proc/mounts.
>
> But this isn't scientific. Is there a predictable logic? Is it always
> the lowest devid?
>
It is the lowest devid which is present (ignoring "missing" devices).
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-12-19 6:52 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-12-18 21:42 what determines what /dev/ is mounted? Chris Murphy
2020-12-19 6:51 ` Andrei Borzenkov
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.