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 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
