All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: helmut@hullen.de
Cc: linux-btrfs@vger.kernel.org
Subject: Re: INSTALL hint: create device btrfs-control
Date: Thu, 4 Aug 2011 22:49:50 +0100	[thread overview]
Message-ID: <20110804214950.GC8970@carfax.org.uk> (raw)
In-Reply-To: <BrDfft7D1uB@helmut.hullen.de>

[-- Attachment #1: Type: text/plain, Size: 1695 bytes --]

   Hi, Helmut,

On Thu, Aug 04, 2011 at 11:26:00PM +0200, Helmut Hullen wrote:
> Du meintest am 04.08.11:
> >> 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 ...

   Well, it's probably OK just to use this particular symptom for
now. You've generally got to run btrfs dev scan before you run
anything else, so that message should turn up. I wouldn't spend ages
hunting down additional failure messages.

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

   Yes, I think there is a problem with it at the moment. The usual
one that happens every so often. I don't know what's up, but it seems
to be something to do with the MySQL back-end.

   At least the text looks good to you, so we'll leave it at that for
now, and it should be better the next time the kernel.org admins sort
it out.

   Hugo.

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
  --- "What's so bad about being drunk?" "You ask a glass of water" ---  
                                                                         

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

  reply	other threads:[~2011-08-04 21:49 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
2011-08-04 21:49         ` Hugo Mills [this message]
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=20110804214950.GC8970@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.