From: Hullen@t-online.de (Helmut Hullen)
To: linux-btrfs@vger.kernel.org
Subject: Re: looking for non existent devices
Date: 21 Mar 2012 19:24:00 +0100 [thread overview]
Message-ID: <C5J2uwYuCXB@helmut.hullen.de> (raw)
In-Reply-To: <20120321181202.GA1973@zambezi.lan>
Hallo, Ilya,
Du meintest am 21.03.12:
>> 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
> I think this has been fixed in recent btrfs-progs, commit 32eff711.
It is fixed in some (or many) places, it is not fixed everywhere. I had
used kernel 3.2.9
Viele Gruesse!
Helmut
next prev parent reply other threads:[~2012-03-21 18:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-17 9:32 looking for non existent devices Helmut Hullen
2012-03-21 18:12 ` Ilya Dryomov
2012-03-21 18:24 ` Helmut Hullen [this message]
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=C5J2uwYuCXB@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).