From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: a.t.hild@gmail.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Fi corruption on RAID1, generation doesn't match
Date: Sun, 7 Feb 2016 22:27:52 +0800 [thread overview]
Message-ID: <56B75468.7070109@gmx.com> (raw)
In-Reply-To: <CAEm4gg=n0bib28HwEBGwzDMg3=O525s6p=YdDqubfPQ_LL-SPg@mail.gmail.com>
On 02/07/2016 10:23 PM, Andreas Hild wrote:
> On 7 February 2016 at 20:56, Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
>>
>> You are wondering why data is still 168G, but that's the allocated data
>> chunk size.
>>
>> It means 168G space is allocated to store data, but only 42M is used.
>> Matches with your vanilla df output.
>>
>> So it doesn't mean you data are still here.
>
> I understand now. Thanks very much!
>
>
> [...]
>>
>> That's the previous transaction's tree root.
>> If you are in good luck, previous trans may has all your data.
>> But if you are in bad luck, it may already after the remove.
>>
>> Normally, at least something should still be in previous trans.
>>
>> Now use btrfsck to check if previous trans is in good shape.
>>
>> # btrfsck --tree-root 647630028800
>>
>> If btrfsck only reports minor problems, like space cache tree mismatch, then
>> it means previous trans are almost OK.
>>
>> Then let btrfsck to revert to previous trans:
>>
>> # btrfsck --tree-root 647630028800 --repair
>>
>> If you're really in good luck, then you can mount the fs and found something
>> in it.
>
>
> Great! I'll try this.
>
> The 'tree-root' option must be a recent development. My 'stable'
> Debian live disk does not recognize this option.
>
> Could any one recommended a live disk that already includes this btrfsck option?
>
> Many thanks!
>
> Andreas
>
Try latest installation ISO from Archlinux, which should be recent
enough, if not already latest.
Another recommendation should be latest Fedora, which should be no later
than Arch.
But with a better LiveCD environment, like with GUI, other than pure CLI
from Archlinux ISO.
Thanks,
Qu
next prev parent reply other threads:[~2016-02-07 14:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-07 13:15 Fi corruption on RAID1, generation doesn't match Andreas Hild
2016-02-07 13:27 ` Lionel Bouton
2016-02-07 13:41 ` Andreas Hild
2016-02-07 13:56 ` Qu Wenruo
2016-02-07 14:23 ` Andreas Hild
2016-02-07 14:27 ` Qu Wenruo [this message]
2016-02-07 16:21 ` Andreas Hild
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=56B75468.7070109@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=a.t.hild@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.