doesn't match, kernel won't
>>> be able to delete it.
>>>
>>> btrfs-progs check-next branch can handle it, but you need to ensure
>>> there is no other bugs.
>>>
>>> So, you still need to compile the latest btrfs-p
reventing to
> > mount filsystem in higher kernel versions
> > ср, 12 дек. 2018 г. в 16:26, Qu Wenruo <mailto:quwenruo.bt...@gmx.com>>:
> >>
> >>
> >>
> >> On 2018/12/12 下午9:00, Nikolay Borisov wrote:
&g
On 2018/12/12 下午9:00, Nikolay Borisov wrote:
>
>
> On 12.12.18 г. 14:44 ч., Олег Власов wrote:
>> Hello
>> If anyone could help with with "name hash mismatch" error at btrfs.
>> full error is
>> "BTRFS critical (device sda5): corrupt leaf: r
On 12.12.18 г. 14:44 ч., Олег Власов wrote:
> Hello
> If anyone could help with with "name hash mismatch" error at btrfs.
> full error is
> "BTRFS critical (device sda5): corrupt leaf: root=2234
> block=244700761008 slot 136 ino=2531, name hash mismatch with k
Hello
If anyone could help with with "name hash mismatch" error at btrfs.
full error is
"BTRFS critical (device sda5): corrupt leaf: root=2234
block=244700761008 slot 136 ino=2531, name hash mismatch with key,
have 0x0026cd84d"
so i could not access one file neither to
Hi!
I'm running btrfs on a bcache device, for now, it performed flawlessly.
Yesterday, however, during backup, I found the following errors in the
journal:
BTRFS critical (device bcache0): corrupt leaf: root=1 block=367591424
slot=1 ino=10085264, name hash mismatch with key,
