All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Gamari <bgamari.foss@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Recovering data from disk with loose cable
Date: Fri, 11 Feb 2011 11:16:41 -0500	[thread overview]
Message-ID: <87pqqyczrp.fsf@gmail.com> (raw)
In-Reply-To: <AANLkTinsT-FRkV0Ja63YCqCn2OWdZnYORxPFgKm4DxQW@mail.gmail.com>

On Wed, 9 Feb 2011 21:46:38 -0500, Ben Gamari <bgamari@gmail.com> wrote:
> We have a disk array behind two external SATA port multipliers (four
> disks on each multiplier) which has been running btrfs (RAID 1 for
> both data and metadata). Unfortunately, earlier today it seems one of
> the SATA cables came loose, resulting in the kernel (2.6.37)
> eventually OOPSing although apparently not before writing quite a bit
> of data. Upon reboot, I was met with the dreaded,
> 
>     disk-io.c:741: open_ctree_fd: Assertion `!(!tree_root->node)' failed.
> 
> Unfortunately any attempt to run any of the btrfs-progs utilities
> (from git) met a similar end. There was recently a patch to try harder
> in recovering from this problem posted to the list[1], although
> unfortunately it is unable to find a root. Considering there are eight
> disks in the array and only four were affected by the loose cable, I
> find it very hard to believe there is no way to recover this volume.
> Any suggestions at all would be greatly appreciated. Recovering this
> data would mean a lot. Thanks,
> 
Given there has been no response to this, I suppose I should assume this
data is unrecoverable? It's not the end of the world if so, but again,
it would be nice to get a few files and it seems like a small subset of
the metadata is corrupted.

Cheers,

- Ben

      reply	other threads:[~2011-02-11 16:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-10  2:46 Recovering data from disk with loose cable Ben Gamari
2011-02-11 16:16 ` Ben Gamari [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=87pqqyczrp.fsf@gmail.com \
    --to=bgamari.foss@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.