From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: INSTALL hint: create device btrfs-control
Date: 04 Aug 2011 23:26:00 +0200 [thread overview]
Message-ID: <BrDfft7D1uB@helmut.hullen.de> (raw)
In-Reply-To: <20110804204219.GB8970@carfax.org.uk>
Hallo, Hugo,
Du meintest am 04.08.11:
>> ...
>> failed to read /dev/hdc
>> failed to read /dev/hdc8
>> failed to read /dev/lmscd
>> failed to read /dev/sdc1
>> failed to read /dev/sdb4
>> failed to open /dev/btrfs-control skipping device registration
> OK, that's the symptom we can put in the problems list for this
> particular issue.
[...]
> Goffredo published a patch to scan only the contents of
> /proc/partitions, which should at least shut up the scan over the
> issue of non-existent devices in /dev. That's in the next
> integration-* branch (going out shortly... I'm just integrating and
> updating the balance management patches before i release).
That sounds fine - thanks to you and to Goffredo!
>> I'll try to reproduce these messages ...
> Thanks. We can add those as symptoms to the solution later.
I've just run the first test - finding reliable (for only this case)
messages is a bad job ...
> How's this?
> https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#I_get_the_message
> _.22failed_to_open_.2Fdev.2Fbtrfs-control_skipping_device_registratio
> n.22_from_.22btrfs_dev_scan.22
There's some problem in the Wiki. This new paragraph (?) is not shown
when I call the "Problem_FAQ", it ends with the "Copy-on-write doesn't
work" question.
When I look into the source code of that page I can see and read the
paragraph, and it looks fine!
Viele Gruesse!
Helmut
next prev parent reply other threads:[~2011-08-04 21:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 10:10 INSTALL hint: create device btrfs-control Helmut Hullen
2011-08-04 17:35 ` Hugo Mills
2011-08-04 18:35 ` Helmut Hullen
2011-08-04 20:13 ` Helmut Hullen
2011-08-04 20:42 ` Hugo Mills
2011-08-04 21:26 ` Helmut Hullen [this message]
2011-08-04 21:49 ` Hugo Mills
2011-08-05 5:43 ` Helmut Hullen
2011-08-05 10:19 ` 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=BrDfft7D1uB@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