From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs listing is wrong
Date: Thu, 11 Sep 2014 18:11:48 +0000 (UTC) [thread overview]
Message-ID: <pan$84b37$6431c22$f05e1b59$2186100a@cox.net> (raw)
In-Reply-To: 5411B5A6.50103@intellasoft.net
Mark Murawski posted on Thu, 11 Sep 2014 10:45:58 -0400 as excerpted:
> Label: 'Root' uuid: d71404d4-468e-47d5-8f06-3b65fa7776aa
> Total devices 2 FS bytes used 7.46GiB
> devid 1 size 9.31GiB used 8.06GiB path /dev/sdh6
> devid 3 size 9.31GiB used 8.06GiB path
> /dev/disk/by-uuid/d71404d4-468e-47d5-8f06-3b65fa7776aa
>
> # ls -al /dev/disk/by-uuid/d71404d4-468e-47d5-8f06-3b65fa7776aa
> lrwxrwxrwx 1 root root 10 Sep 11 10:43
> /dev/disk/by-uuid/d71404d4-468e-47d5-8f06-3b65fa7776aa -> ../../sdh6
>
> devid 3 should really be showing /dev/sde6
I believe that's an instance of a known bug (or depending on how you look
at it possibly two) with a recently posted patch, but I doubt it has made
it to mainline just yet.
What they're going to do is resolve to the canonical paths. They don't
do that at this point, and the paths can change, sometimes showing the
wrong one for certain devices.
I'm not sure the fix will make it into this kernel cycle, however. It
should make it into 3.18 in any case, and will likely be stable-backported
after that.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-09-11 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 14:45 btrfs listing is wrong Mark Murawski
2014-09-11 18:11 ` Duncan [this message]
2014-09-13 6:27 ` Anand Jain
2014-09-17 4:22 ` Mark Murawski
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='pan$84b37$6431c22$f05e1b59$2186100a@cox.net' \
--to=1i5t5.duncan@cox.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).