Re: FS unmountable after RAID/LVM problems

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

 



Qu Wenruo <quwenruo.btrfs@xxxxxxx> writes:

> On 2018年03月13日 16:53, Dirk Gouders wrote:

<SNIP>

>> find-root:
>> 
>> # btrfs-find-root /dev/loop0p1
>> Superblock thinks the generation is 9858294
>> Superblock thinks the level is 1
>> Found tree root at 848773120 gen 9858294 level 1
>
> Tree root is found, find-root won't help much here.
> And if it's really tree root corruption, we should have some kernel
> message for it.
>
>> Well block 832045056(gen: 9858272 level: 1) seems good, but generation/level doesn't match, want gen: 9858294 level: 1
>
> Especially when the next tree block is 22 generation older.
>
> Would you please try to call "btrfs inspect dump-tree <device>" and
> paste the result with *stderr*?
>
> At least we could know which tree block is corrupted.

Here is the result of inspect:

# btrfs inspect dump-tree /dev/loop0p1
btrfs-progs v4.15
checksum verify failed on 363069440 found 296FB15A wanted F0AFE59D
checksum verify failed on 363069440 found 296FB15A wanted F0AFE59D
checksum verify failed on 363069440 found DC09290B wanted C630FD61
checksum verify failed on 363069440 found 296FB15A wanted F0AFE59D
bytenr mismatch, want=363069440, have=17552567724568668829
ERROR: unable to open /dev/loop0p1

Thanks,

Dirk
--
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