* 2 year old raid1 issue chunk-recovery help
@ 2014-01-15 19:40 Vladi Gergov
2014-01-16 2:10 ` Miao Xie
0 siblings, 1 reply; 6+ messages in thread
From: Vladi Gergov @ 2014-01-15 19:40 UTC (permalink / raw)
To: linux-btrfs; +Cc: miaox
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!
--
,-| Vladi
`-| Gergov
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2 year old raid1 issue chunk-recovery help
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
0 siblings, 1 reply; 6+ messages in thread
From: Miao Xie @ 2014-01-16 2:10 UTC (permalink / raw)
To: Vladi Gergov, linux-btrfs
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2 year old raid1 issue chunk-recovery help
2014-01-16 2:10 ` Miao Xie
@ 2014-01-16 18:20 ` Vladi Gergov
2014-01-17 2:27 ` Miao Xie
0 siblings, 1 reply; 6+ messages in thread
From: Vladi Gergov @ 2014-01-16 18:20 UTC (permalink / raw)
To: Miao Xie; +Cc: linux-btrfs
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.
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
>
--
,-| Vladi
`-| Gergov
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2 year old raid1 issue chunk-recovery help
2014-01-16 18:20 ` Vladi Gergov
@ 2014-01-17 2:27 ` Miao Xie
2014-01-17 16:52 ` Vladi Gergov
0 siblings, 1 reply; 6+ messages in thread
From: Miao Xie @ 2014-01-17 2:27 UTC (permalink / raw)
To: Vladi Gergov; +Cc: linux-btrfs
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
>>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2 year old raid1 issue chunk-recovery help
2014-01-17 2:27 ` Miao Xie
@ 2014-01-17 16:52 ` Vladi Gergov
2014-01-20 2:32 ` Miao Xie
0 siblings, 1 reply; 6+ messages in thread
From: Vladi Gergov @ 2014-01-17 16:52 UTC (permalink / raw)
To: Miao Xie; +Cc: linux-btrfs
Hi,
Not sure if my previous email was received as I sent it from my phone. I
had to dd the disk off and then losetup mount the image. What do you
mean by erase the data on loop7? I have tried to mount separately without
success.
On Friday, 17.01.14 at 10:27, Miao Xie wrote:
> 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
> >>
> >
>
--
,-| Vladi
`-| Gergov
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2 year old raid1 issue chunk-recovery help
2014-01-17 16:52 ` Vladi Gergov
@ 2014-01-20 2:32 ` Miao Xie
0 siblings, 0 replies; 6+ messages in thread
From: Miao Xie @ 2014-01-20 2:32 UTC (permalink / raw)
To: Vladi Gergov; +Cc: linux-btrfs
On fri, 17 Jan 2014 08:52:55 -0800, Vladi Gergov wrote:
> Not sure if my previous email was received as I sent it from my phone. I
> had to dd the disk off and then losetup mount the image. What do you
> mean by erase the data on loop7? I have tried to mount separately without
> success.
When we mount a btrfs filesystem, the kernel will find out all the devices that
belongs to the filesystem by searching all the devices and comparing fs uuid in
the super block. So I think you can erase the super block data in loop7 to prevent
it being found since it broken the mount. But I made a mistake, actually you needn't
erase the data on loop7, just detach it.
BTW, I have tried the method I said below on my box, and the device was replaced
successfully.
# mkfs.btrfs -d raid1 -m raid1 <dev1> <dev2>
# mount <dev1> <mnt>
# dd if=<in> of=<mnt>/<out> bs=1M count=1024
# umount <mnt>
# unplug <dev2>
# mount <dev1> -o degraded <mnt>
# btrfs replace start missing <new_dev>
Thanks
Miao
>
> On Friday, 17.01.14 at 10:27, Miao Xie wrote:
>> 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
>>>>
>>>
>>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2014-01-20 2:30 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2014-01-17 16:52 ` Vladi Gergov
2014-01-20 2:32 ` Miao Xie
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.