From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: what determines what /dev/ is mounted?
Date: Sat, 19 Dec 2020 09:51:39 +0300 [thread overview]
Message-ID: <e6821f22-8bd6-a827-2ddd-7d45e0d3d6f1@gmail.com> (raw)
In-Reply-To: <CAJCQCtQiaAvNGKUiz28jBiw67rSJWp+Ei2uGet2F=xyaziu0nQ@mail.gmail.com>
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).
prev parent reply other threads:[~2020-12-19 6:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 21:42 what determines what /dev/ is mounted? Chris Murphy
2020-12-19 6:51 ` Andrei Borzenkov [this message]
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=e6821f22-8bd6-a827-2ddd-7d45e0d3d6f1@gmail.com \
--to=arvidjaar@gmail.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