Re: BTRFS disaster (of my own making). Is this recoverable?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Out of frustration and vodka I tried:

btrfs check --repair /dev/sde

To instantly be met with:

enabling repair mode
checksum verify failed on 20971520 found 8B1D9672 wanted 2F8A4238
checksum verify failed on 20971520 found 8B1D9672 wanted 2F8A4238
bytenr mismatch, want=20971520, have=8330001001141004672
Couldn't read chunk root
Couldn't open file system



On Mon, Aug 3, 2015 at 10:20 PM, Sonic <sonicsmith@xxxxxxxxx> wrote:
> On Mon, Aug 3, 2015 at 12:32 PM, Sonic <sonicsmith@xxxxxxxxx> wrote:
>> btrfs rescue chunk-recover
>
> Ran this:
> btrfs rescue chunk-recover -v /dev/sde |tee brcr.txt
>
> Got this (very end of output):
> ==================================
> Unrecoverable Chunks:
>
> Total Chunks:           3292
>   Recoverable:          3292
>   Unrecoverable:        0
>
> Orphan Block Groups:
>
> Orphan Device Extents:
>
> Fail to recover the chunk tree.
> ==================================
> If earlier output of this process might be helpful I can provide it
> (used tee to create a file).
>
> Didn't work - seems all chunks found were recoverable - it's
> apparently the missing chunks that are the problem.
>
> I'm thinking this is a lost cause. Also thinking I need to provide for
> some redundancy in the future :-)
>
> Any other suggestions before I give up the ghost on this?
>
> Thanks,
>
> Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux