linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Shane Shrybman <shrybman@teksavvy.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Oops while rebalancing, now unmountable.
Date: Mon, 08 Nov 2010 16:04:28 -0500	[thread overview]
Message-ID: <1289250095-sup-1814@think> (raw)
In-Reply-To: <1289248765.3611.6.camel@mars>

Excerpts from Shane Shrybman's message of 2010-11-08 15:39:25 -0500:
> On Mon, 2010-11-08 at 12:55 -0500, Chris Mason wrote:
> > Excerpts from Shane Shrybman's message of 2010-11-08 12:10:57 -0500:
> > > Hi,
> > > 
> > > Got an oops last week while rebalancing that seems to have left me with
> > > a corrupted btrfs. Kernel was ~2.6.36 + Transparent hugetlb patchset +
> > > small misc. patchs.
> > 
> > Have you tried the 2.6.36 + the btrfs unstable git tree?  It may be able
> > to help here.
> 
> Ok, I have built and booted the 2.6.36 + the btrfs unstable git tree
> kernel and ran btrfsck with the same results.
> 
> # btrfsck /dev/sdc1
> checksum verify failed on 625055924224 wanted C3DFFE41 found 9F99998
> checksum verify failed on 625055924224 wanted C3DFFE41 found 9F99998
> checksum verify failed on 625055924224 wanted C3DFFE41 found 9F99998
> Segmentation fault

Ok, if you pull down the latest btrfs-progs from git, you'll find a new
option to btrfsck, which tries alternate copies of the super block.

btrfsck -s 1 /dev/sdc1
btrfsck -s 2 /dev/sdc1
btrfsck -s 3 /dev/sdc1

If we're really lucky, one of these will work.

-chris

  reply	other threads:[~2010-11-08 21:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-08 17:10 Oops while rebalancing, now unmountable Shane Shrybman
2010-11-08 17:55 ` Chris Mason
2010-11-08 20:39   ` Shane Shrybman
2010-11-08 21:04     ` Chris Mason [this message]
2010-11-08 21:25       ` Shane Shrybman
2010-11-09 13:42 ` Chris Mason
2010-11-09 18:21   ` Shane Shrybman
2010-11-14 19:55     ` Shane Shrybman
2010-11-14 20:42       ` Andrea Arcangeli
2010-11-14 22:00         ` Christoph Hellwig
2010-11-14 22:12           ` Andrea Arcangeli
2010-11-15 18:23             ` Christoph Hellwig
2010-11-15 18:46               ` Chris Mason
2010-11-15 19:03                 ` Christoph Hellwig
2010-11-16 21:48                 ` Shane Shrybman
2010-11-15 18:46               ` Andrea Arcangeli
2010-11-15 19:03                 ` Chris Mason
2010-11-15 19:16                   ` Andrea Arcangeli
2010-11-15 19:12                 ` Christoph Hellwig
2010-11-15 19:18                   ` Chris Mason
2010-11-15 19:29                   ` Andrea Arcangeli
2010-11-15 20:54                     ` Christoph Hellwig

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=1289250095-sup-1814@think \
    --to=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=shrybman@teksavvy.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).