From: Chris Samuel <chris@csamuel.org>
To: Hugo Mills <hugo@carfax.org.uk>, Not Zippy <notzippy@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: btrfs: open_ctree failed
Date: Tue, 27 Mar 2012 11:20:55 +1100 [thread overview]
Message-ID: <4F7107E7.8050908@csamuel.org> (raw)
In-Reply-To: <20120326224729.GB2597@carfax.org.uk>
On 27/03/12 09:47, Hugo Mills wrote:
> I'd definitely recommend running as recent a kernel as you can --
> either the last released (3.3 in this case)
I'm not sure I'd recommend 3.3; there were a number of reports of a
regression regarding preamture ENOSPC in that code which was bisected to
a particular change but I didn't see any evidence of it being fixed in
3.3 (only 2 unrelated fixes were merged after rc6, where this problem
was confirmed).
https://lkml.org/lkml/2012/3/9/624
I'm currently running 3.2.13 from the Ubuntu site here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/
I just download the deb via Lynx and install it with dpkg -i $PACKAGE.
cheers,
Chris
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
next prev parent reply other threads:[~2012-03-27 0:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANDob0+rwkLGeJg4kP+TpPpN8VOdrOV684F5YiLC6+BkzYehHA@mail.gmail.com>
2012-03-26 21:40 ` btrfs: open_ctree failed Not Zippy
2012-03-26 21:57 ` Hugo Mills
2012-03-26 22:36 ` Not Zippy
2012-03-26 22:47 ` Hugo Mills
2012-03-27 0:20 ` Chris Samuel [this message]
2012-03-27 12:58 ` Not Zippy
2012-03-27 13:02 ` Hugo Mills
2012-03-27 15:21 ` Not Zippy
2012-03-27 17:37 ` Not Zippy
[not found] <4EE6C49A.5070600@genome.wustl.edu>
2011-12-14 22:43 ` Samuel Just
[not found] <CAPXeO6QbDxyoqYRhXxMGvc9JYQ6TZrTF7MwCNg-xdU-MgCQU3w@mail.gmail.com>
2011-07-07 9:20 ` Yulin, Denis
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=4F7107E7.8050908@csamuel.org \
--to=chris@csamuel.org \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=notzippy@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).