From: Chris Mason <chris.mason@oracle.com>
To: Simon Kirby <sim@hostway.ca>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: 2.6.35.4 fumble-spolision
Date: Thu, 9 Sep 2010 20:49:09 -0400 [thread overview]
Message-ID: <20100910004909.GX3227@think> (raw)
In-Reply-To: <20100910001703.GF26862@hostway.ca>
On Thu, Sep 09, 2010 at 05:17:03PM -0700, Simon Kirby wrote:
> Hello!
>
> We seem to have done something to our backup volumes while switching
> between 2.6.33.2 and 2.6.35.4 which is now causing this crash while
> booting either kernel and mounting one of the volumes. Crash from
> 3.6.35.4 plus Li Zefan's free-space-cache.c patches. extent-tree.c
> is untouched, but if needed, we can try again with clean 2.6.35.4.
What does btrfsck say? Does the problem go away in 2.6.33?
-chris
next prev parent reply other threads:[~2010-09-10 0:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 0:17 2.6.35.4 fumble-spolision Simon Kirby
2010-09-10 0:49 ` Chris Mason [this message]
2010-09-10 7:54 ` Simon Kirby
2010-09-10 8:21 ` Yan, Zheng
2010-09-10 16:50 ` Simon Kirby
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=20100910004909.GX3227@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sim@hostway.ca \
/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).