linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Cavnar <alc6379@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: bad tree block after power loss during rebalance
Date: Sat, 14 Aug 2010 19:13:08 -0500	[thread overview]
Message-ID: <AANLkTin3UApRG_VNNrmOZ3g5q7Wq1pWg3KGi6uKd-0_C@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikog8ukHjdQjAA6d6S6egrXbNFPjKD2xuTW71Gn@mail.gmail.com>

Greetings,

Is there anyone who could help me with this issue? I know there's no
btrfsck, but is there something I can possibly do to recover this
volume?

Thanks,
Alex

On Mon, Jul 26, 2010 at 4:09 PM, Alex Cavnar <alc6379@gmail.com> wrote:
> Hey all,
>
> I have a 3TB array I'm running via MD with a BTRFS filesystem on it. I
> lost power during a rebalance, and now when I attempt to mount it, I
> get this error in dmesg:
>
> (This is attempting to mount with -o degraded option)
>
> Jul 26 15:56:36 NASBOX kernel: [234228.548197] btrfs: open_ctree failed
> Jul 26 16:00:37 NASBOX kernel: [234469.584064] device fsid
> fb481f12aed8508d-bf298b2f357984bf devid 1 transid 36802
> /dev/mapper/vg--raid-lv--storage
> Jul 26 16:00:37 NASBOX kernel: [234469.584490] btrfs: allowing degraded mounts
> Jul 26 16:00:39 NASBOX kernel: [234471.703955] btrfs bad tree block
> start 6949838612584515097 241665916928
> Jul 26 16:00:39 NASBOX kernel: [234471.724204] btrfs: open_ctree failed
>
> Any pointers to get this to mount? I know that btrfsck doesn't fix
> anything, but is there something I can do to recover this volume?
> There is some data I'd like to get off that I'd placed on between
> backups.
>
> Thanks!
> Alex Cavnar
>

      reply	other threads:[~2010-08-15  0:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26 21:09 bad tree block after power loss during rebalance Alex Cavnar
2010-08-15  0:13 ` Alex Cavnar [this message]

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=AANLkTin3UApRG_VNNrmOZ3g5q7Wq1pWg3KGi6uKd-0_C@mail.gmail.com \
    --to=alc6379@gmail.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).