From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs still looks for not existing devices
Date: 14 Oct 2011 16:17:00 +0200 [thread overview]
Message-ID: <BvpRM+hT1uB@helmut.hullen.de> (raw)
In-Reply-To: <20111014140516.GJ21931@carfax.org.uk>
Hallo, Hugo,
Du meintest am 14.10.11:
>> 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).
Sorry - bending the fingers is a hard work ... (and looking for typos
too ...)
> 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.
Ok - have I to cross my fingers?
Viele Gruesse!
Helmut
next prev parent reply other threads:[~2011-10-14 14:17 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
2011-10-14 14:17 ` Helmut Hullen [this message]
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=BvpRM+hT1uB@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