Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: helmut@hullen.de
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs still looks for not existing devices
Date: Fri, 14 Oct 2011 15:05:16 +0100	[thread overview]
Message-ID: <20111014140516.GJ21931@carfax.org.uk> (raw)
In-Reply-To: <BvpREOmi1uB@helmut.hullen.de>

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

On Fri, Oct 14, 2011 at 03:51:00PM +0200, Helmut Hullen wrote:
> Hallo, linux-btrfs,
> 
> I've just compiled kernel 3.9.04 and run

   Do you mean 3.0.4? We've not reached 3.2 yet, let alone 3.9 :) (Not
that it matters in this case).

>         btrfs filesystem show
> 
> On my system (Slackware 13.37, self made, without "udev") it still shows  
> a lot of non existent devices (I have shortened the list ...):

   This is not a kernel issue, it's a purely userspace issue. Try the
latest integration branch from git.darksatanic.net, which should have
a fix for it.

   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
        --- emacs:  Eighty Megabytes And Constantly Swapping. ---        

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

  reply	other threads:[~2011-10-14 14:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-14 13:51 btrfs still looks for not existing devices Helmut Hullen
2011-10-14 14:05 ` Hugo Mills [this message]
2011-10-14 14:17   ` Helmut Hullen
2011-10-14 14:59   ` Helmut Hullen
2011-10-14 15:08     ` Hugo Mills
     [not found]       ` <20111014151432.GA19381@mother.jarsat.pl>
2011-10-14 15:21         ` Hugo Mills
2011-10-14 15:43       ` Helmut Hullen
2011-10-14 21:26         ` Goffredo Baroncelli
2011-10-15  2:57           ` Helmut Hullen
2011-10-21  8:21   ` 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=20111014140516.GJ21931@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox