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: looking for non existent devices
Date: 17 Mar 2012 10:32:00 +0100	[thread overview]
Message-ID: <C52pIRfT1uB@helmut.hullen.de> (raw)

Hallo, linux-btrfs,

some commands still look for non existent devices.

I don't use "udev".
When I run

        btrfs filesystem show

only the existent devices are shown - fine.

When I run

        btrfs filesystem label

or

        btrfs scrub status /dev/sdxn

then I get a lot of error messages with (p.e.)

  failed to read /dev/hda6: No such device or address
  failed to read /dev/sdm7: No such device or address
  failed to read /dev/sr3: No such device or address

Kernel 3.2.9

Viele Gruesse!
Helmut

             reply	other threads:[~2012-03-17  9:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-17  9:32 Helmut Hullen [this message]
2012-03-21 18:12 ` looking for non existent devices Ilya Dryomov
2012-03-21 18:24   ` Helmut Hullen
2012-03-21 18:52     ` Ilya Dryomov
2012-03-21 19:26       ` Helmut Hullen

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=C52pIRfT1uB@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).