linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs device scan
Date: 12 May 2011 08:25:00 +0200	[thread overview]
Message-ID: <BljOne7T1uB@helmut.hullen.de> (raw)
In-Reply-To: <4DCB7195.30208@gmail.com>

Hallo, Victor,

Du meintest am 12.05.11:

>>> I have a couple computers running 2.6.38
>>> (Ubuntu Natty 2.6.38-8-generic), and on both of them
>>> "btrfs device scan" comes back with nothing other than
>>> "failed to read /dev/sr0"

[..]

> $ btrfs device scan
> Scanning for Btrfs filesystems
> failed to read /dev/sr0

That's a "well known" error; "scan" tries block devices which really  
cannot contain a btrfs filesystem.
People who don't use "udev" get a lot of more "failed to read" messages;  
"scan" seems to try every block device which exists in "/dev".

Maybe it's more reliable if "scan" doesn't look into "dev" but uses "/ 
proc/partitions".

> $ btrfs filesystem show
> failed to read /dev/sr0
> Label: 'server-backup'  uuid: b927ead9-2e5b-4ee8-b9f4-7209177c49d8
> 	Total devices 2 FS bytes used 603.17GB
> 	devid    1 size 1.36TB used 605.28GB path /dev/sdb1
> 	devid    2 size 1.36TB used 605.26GB path /dev/sdc1

That shows that (in this case) you can ignore the "scan" message.

Viele Gruesse!
Helmut

  reply	other threads:[~2011-05-12  6:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-12  4:26 btrfs device scan Victor Roetman
2011-05-12  4:46 ` Helmut Hullen
2011-05-12  5:35   ` Victor Roetman
2011-05-12  6:25     ` Helmut Hullen [this message]
2011-05-12  6:04 ` Arne Jansen

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=BljOne7T1uB@helmut.hullen.de \
    --to=hullen@t-online.de \
    --cc=helmut@hullen.de \
    --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).