From: Sami Haahtinen <sami@haahtinen.name>
To: dave@jikos.cz, Hugo Mills <hugo@carfax.org.uk>,
Sami Haahtinen <sami@haahtinen.name>,
linux-btrfs@vger.kernel.org
Subject: Re: Rebuilding chunk root?
Date: Mon, 24 Sep 2012 19:43:16 +0300 [thread overview]
Message-ID: <CA+nK0aMQdoO56R_YpuQjw=7iuee2ReFCwLw853RYXV1jU2a6hg@mail.gmail.com> (raw)
In-Reply-To: <20120924151203.GI14582@twin.jikos.cz>
On Mon, Sep 24, 2012 at 6:12 PM, David Sterba <dave@jikos.cz> wrote:
> On Mon, Sep 24, 2012 at 03:02:39PM +0100, Hugo Mills wrote:
> > Out of interest, does mounting with -o recovery help at all? (I'm
> > not expecting it to do much if your chunk tree's gone, but it might do
> > something).
>
> The -o recovery has access to the respective tree roots, but the
> contents may be destroyed already. The chunk tree is not deep, I can see
> height 1 on a 6 disk array (though lightly used, 1 node, 8 leaves) and 3
> disk array (1/7 TB used, 1 node, 29 leaves). So it's quite a small
> amount of data to destroy the chunktree completely, COW will lower the
> chances a bit.
Yeah, the whole tree is gone, I'm pretty sure of it since the first
20-50GB has been wiped from the drive and the mentioned address is in
the beginning of that part. I just wonder if there is any chance of
the older versions of the chunk tree still being somewhere and how to
find them. I doubt it's an easy feat though.
> Rebuilding from scratch does not look simple, the available information
> is stored in BLOCK_GROUP_ITEMs or INODE_ITEMs and covers portions of the
> chunks. Given that the device tree would be probably damaged as well,
> the amount of information to do cross-check is not high. Maybe replaying
> the chunk creation logic can save some guesswork.
Replaying chunk creation logic would not help that much, since the
drive has been resized a few times and had other operations that have
modified the chunk tree as well. The array itself is not that complex
(2 drives), but it's still not as simple as a single drive array.
Regards,
--
Sami Haahtinen
Bad Wolf Oy
+358443302775
prev parent reply other threads:[~2012-09-24 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 13:28 Rebuilding chunk root? Sami Haahtinen
2012-09-24 14:02 ` Hugo Mills
2012-09-24 15:12 ` David Sterba
2012-09-24 16:43 ` Sami Haahtinen [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='CA+nK0aMQdoO56R_YpuQjw=7iuee2ReFCwLw853RYXV1jU2a6hg@mail.gmail.com' \
--to=sami@haahtinen.name \
--cc=dave@jikos.cz \
--cc=hugo@carfax.org.uk \
--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).