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 21:42:20 +0100	[thread overview]
Message-ID: <20110804204219.GB8970@carfax.org.uk> (raw)
In-Reply-To: <BrDfVHaT1uB@helmut.hullen.de>

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

On Thu, Aug 04, 2011 at 10:13:00PM +0200, Helmut Hullen wrote:
> Hallo, Hugo,
> 
> Du meintest am 04.08.11:
> 
> >    What are the symptoms of not having the device node? (i.e. how
> > would I diagnose this particular problem?)
> 
> The days get shorter and shorter ...
> 
> running
> 
>         btrfs device scan
> 
> produces something like
> 
> ...
> 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.

> failed to read /dev/sdd8
> failed to read /dev/hdc9
> failed to read /dev/sdf8
> ...
> 
> a lot of error messages for not existing devices and 1 error messages on  
> behalf of "btrfs-control".
> 
> My "/dev" directory has worked (without "udev") without any problem for  
> more than 10 years, it contains (has contained) a lot of entries for  
> nearly every case of disk. Therefore i had started with
> 
>         btrfs device scan 2>/dev/null
> 
> and that deleted the "btrfs-control" error message too. And
> 
>         btrfs device scan 2>&1 | grep -v 'failed to'
> 
> didn't help too.

   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).

>         btrfs-show
> 
> doesn't need "/dev/btrfs-control", it shows the existing btrfs  
> partition(s).
> 
> If I remember correct: mounting works, writing works, reading works. And  
> adding another partition works.
> 
> But there are strange messages when I try to resize or delete.
> 
> I'll try to reproduce these messages ...

   Thanks. We can add those as symptoms to the solution later.

   How's this?

https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#I_get_the_message_.22failed_to_open_.2Fdev.2Fbtrfs-control_skipping_device_registration.22_from_.22btrfs_dev_scan.22

   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
       --- "I lost my leg in 1942.  Some bastard stole it in a ---       
                            pub in Pimlico."                             

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

  reply	other threads:[~2011-08-04 20:42 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 [this message]
2011-08-04 21:26       ` Helmut Hullen
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=20110804204219.GB8970@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.