From: "H. Peter Anvin" <hpa@zytor.com>
To: Chris Mason <chris.mason@fusionio.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Device names
Date: Tue, 19 Jun 2012 17:00:11 -0700 [thread overview]
Message-ID: <4FE1128B.5080004@zytor.com> (raw)
In-Reply-To: <20120619235129.GB4102@shiny>
On 06/19/2012 04:51 PM, Chris Mason wrote:
>
> At mount time, we go through and verify the path names still belong to
> the filesystem you thought they belonged to. The bdev is locked during
> the verification, so it won't be able to go away or change.
>
> This is a long way of saying right we don't spit out device numbers.
> Even device numbers can change. We can easily add a uuid based listing,
> which I think is what you want.
>
No, I want to find the actual devices. I know I can get the UUID, but
scanning all the block devices in the system looking for that UUID is a
nonstarter.
Device path names can change while the system is operating (and, worse,
are dependent on namespace changes and chroot); device *numbers* cannot
as long as the device is in use (e.g. mounted.) They can indeed change
while not in use, of course.
-hpa
next prev parent reply other threads:[~2012-06-20 0:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 0:29 Device names H. Peter Anvin
2012-06-19 23:51 ` Chris Mason
2012-06-20 0:00 ` H. Peter Anvin [this message]
2012-06-20 13:37 ` Chris Mason
2012-06-20 17:06 ` Goffredo Baroncelli
-- strict thread matches above, loose matches on Subject: below --
2003-10-19 18:30 device names James Courtier-Dutton
2003-10-20 9:08 ` Clemens Ladisch
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=4FE1128B.5080004@zytor.com \
--to=hpa@zytor.com \
--cc=chris.mason@fusionio.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 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.