linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Diwaker Gupta <diwaker@maginatics.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Error mounting multi-device fs after restart
Date: Tue, 8 Feb 2011 12:25:55 -0800	[thread overview]
Message-ID: <AANLkTikkUFDTiGqRkMk-VtvxSFS3vNGp0QCn=HPef89V@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=vSb0i-joekFrZRmwcAE+5w8FwV2FFWcbMvC6n@mail.gmail.com>

Help, anyone? Sorry for the quick repost, but there was some important
data on that filesystem that I don't have a backup for. I'd really
appreciate any pointers that can help recover the data.

Searching through the archives, it seems others have faced similar
issues due to sudden power outages. AFAIK we did not have any power
outage.

I've run badblocks on all of the 10 drives and three of them had a few
bad blocks. I'm inclined to rule out bad disks as the root cause. In
any case, isn't this exactly the kind of situation btrfs should
protect users against?

A 'btrfsck' aborts on all of the drives. I've tried running it with
'-s 1' as well as '-s 2' with no success. Does that mean that none of
the drives have any copy of the superblock intact?

Diwaker

On Mon, Feb 7, 2011 at 11:46 AM, Diwaker Gupta <diwaker@maginatics.com> wrote:
> Hello,
>
> We have 10 1-TB drives hosting a multi-device btrfs filesystem,
> configured with raid1+0 for both data and metadata. After some package
> upgrades over the weekend I restarted the system and it did not come
> back up afterwards. I booted using a rescue disk and ran btrfsck (next
> branch from Chris's git repository). Unfortunately btrfsck aborts on
> every single drive with errors like this:
>
> parent transid verify failed on 12050980864 wanted 377535 found 128327
> parent transid verify failed on 12074557440 wanted 422817 found 126691
> parent transid verify failed on 12057542656 wanted 422786 found 126395
> parent transid verify failed on 12075556864 wanted 423004 found 126691
> bad block 12095545344
> parent transid verify failed on 12079190016 wanted 422826 found 105147
> leaf parent key incorrect 12097544192
> bad block 12097544192
>
> I'm running 10.04 Ubuntu Lucid with the lts-backport x86_64 kernel:
> 2.6.35-23-server
>
> Attempting to mount the filesystem blocks indefinitely, with
> /var/log/messages getting filled with the 'parent transid verify'
> errors.
>
> IIUC the 'btrfs-select-super' utility is not really helpful in our
> case. At this point, my only priority is to somehow rescue the data
> from the filesystem. I'd really appreciate if someone on the list
> could help me out.
>
> I'm happy to provide any other information required. Please CC me on
> replies as I'm not subscribed to the list.
>
> Thanks,
> Diwaker
>

  reply	other threads:[~2011-02-08 20:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-07 19:46 Error mounting multi-device fs after restart Diwaker Gupta
2011-02-08 20:25 ` Diwaker Gupta [this message]
2011-02-08 21:04   ` Felix Blanke
2011-02-08 21:51   ` Hubert Kario
2011-02-08 21:59     ` Diwaker Gupta
2011-02-08 22:04       ` cwillu
2011-02-08 22:11         ` Diwaker Gupta

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='AANLkTikkUFDTiGqRkMk-VtvxSFS3vNGp0QCn=HPef89V@mail.gmail.com' \
    --to=diwaker@maginatics.com \
    --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;
as well as URLs for NNTP newsgroup(s).