From: Miao Xie <miaox@cn.fujitsu.com>
To: Vladi Gergov <vladi@aresgate.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: 2 year old raid1 issue chunk-recovery help
Date: Fri, 17 Jan 2014 10:27:04 +0800 [thread overview]
Message-ID: <52D894F8.1040300@cn.fujitsu.com> (raw)
In-Reply-To: <20140116182042.GB5425@gypsyops.denof.sin>
On Thu, 16 Jan 2014 10:20:42 -0800, Vladi Gergov wrote:
> Thanks Miao,
>
> I have tried to mount it with -o degraded and -o recovery here is the
> outputs:
>
> [216094.269443] btrfs: device label das4 devid 2 transid 107954
> /dev/loop7
> [216094.281965] btrfs: device label das1 devid 7 transid 1168964
> /dev/sdi
> [216094.313419] btrfs: device label das4 devid 3 transid 107954 /dev/sdj
> [216113.887503] btrfs: device label das4 devid 2 transid 107954
> /dev/loop7
> [216113.888690] btrfs: allowing degraded mounts
> [216113.889440] btrfs: failed to read chunk root on loop7
> [216113.905742] btrfs: open_ctree failed
> [216135.144739] btrfs: device label das4 devid 2 transid 107954
> /dev/loop7
> [216135.145996] btrfs: enabling auto recovery
> [216135.146783] btrfs: failed to read chunk root on loop7
> [216135.155985] btrfs: open_ctree failed
>
> any other suggestions? Thanks again.
Is loop7 used to instead of the bad device /dev/sdi? If so, I think
we should erase the data in the loop7, and then
>> # mount <dev> -o degraded <mnt>
>> # btrfs replace start missing <new_dev>
Thanks
Miao
>
> On Thursday, 16.01.14 at 10:10, Miao Xie wrote:
>> On wed, 15 Jan 2014 11:40:09 -0800, Vladi Gergov wrote:
>>> Hi, in 2010 i had an issue with my raid1 when one drive failed and i
>>> added another drive to the array and tried to rebuild. Here is what bug
>>> I hit according to Chris Mason
>>> http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg06868.html
>>>
>>> I have since updated to lastes btrfs-tools 3.12 + kernel 3.13-rc7 and
>>> attempted an chunk recovery which failed with this
>>> http://bpaste.net/show/168445/
>>>
>>> If anyone can help me get at least some of the data off this bad boy it
>>> would be great! I am cc'ing Miao since his name was thrown under the bus
>>> in irc :). Thanks in advance!
>>>
>>
>> Chunk recover command can only recover the case that the devices are good, only
>> the chunk tree is corrupted. So it is not suitable to fix your issue.
>>
>> I think you can try the replace function if you can mount the device successfully,
>> just like:
>> # mount <dev> -o degraded <mnt>
>> # btrfs replace start missing <new_dev>
>>
>> Thanks
>> Miao
>>
>
next prev parent reply other threads:[~2014-01-17 2:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 19:40 2 year old raid1 issue chunk-recovery help Vladi Gergov
2014-01-16 2:10 ` Miao Xie
2014-01-16 18:20 ` Vladi Gergov
2014-01-17 2:27 ` Miao Xie [this message]
2014-01-17 16:52 ` Vladi Gergov
2014-01-20 2:32 ` Miao Xie
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=52D894F8.1040300@cn.fujitsu.com \
--to=miaox@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=vladi@aresgate.net \
/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.