linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <Anand.Jain@oracle.com>
To: Mark Murawski <markm-lists@intellasoft.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs listing is wrong
Date: Sat, 13 Sep 2014 14:27:23 +0800	[thread overview]
Message-ID: <5413E3CB.4050800@oracle.com> (raw)
In-Reply-To: <5411B5A6.50103@intellasoft.net>



Hi Mark,

> 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

  I hope this taken when Root is mounted, (just for confirmation),
  which means those are read from the btrfs kernel. Not by scanning
  the udev.

> # 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


  when we read /dev/sdh6 it was devid 1.
  When we read /dev/disk/by-uuid/d71404d4-468e-47d5-8f06-3b65fa7776aa it 
was devid 3.

  But udev also says
    /dev/disk/by-uuid/d71404d4-468e-47d5-8f06-3b65fa7776aa
  is nothing but a soft link to /dev/sdh6 !!

  Very strange !  Can you run blkid and show its output ?

  Also by any chance did we do a disk to disk copy ?

> devid 3 should really  be showing /dev/sde6

  A reboot or btrfs kernel module reload might update the stale
  and tell the facts.


Thanks, Anand

  parent reply	other threads:[~2014-09-13  6:23 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
2014-09-13  6:27 ` Anand Jain [this message]
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=5413E3CB.4050800@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=markm-lists@intellasoft.net \
    /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).