On 2018/12/12 下午9:51, Олег Власов wrote: > Could you guide me ? > What should I do after compile latest btrfs-progs? "btrfs check --readonly <device>" and paste the output. Thanks, Qu > > ср, 12 дек. 2018 г., 16:47 Qu Wenruo quwenruo.btrfs@xxxxxxx > <mailto:quwenruo.btrfs@xxxxxxx>: > > > > On 2018/12/12 下午9:36, Олег Власов wrote: > > if there any way to remove that item? > > IIRC kernel can't remove it since the hash 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-progs and then the > check-next branch. > > Thanks, > Qu > > > the file that belong to it is useless for me but it preventing to > > mount filsystem in higher kernel versions > > ср, 12 дек. 2018 г. в 16:26, Qu Wenruo <quwenruo.btrfs@xxxxxxx > <mailto:quwenruo.btrfs@xxxxxxx>>: > >> > >> > >> > >> 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: root=2234 > >>>> block=244700761008 slot 136 ino=2531, name hash mismatch with key, > >>>> have 0x000000000026cd84d" > >>>> so i could not access one file neither to remove it. > >>>> > >>>> uname -a > >>>> Linux linux-wwqj 4.12.14-lp150.12.16-default #1 SMP Tue Aug 14 > >>>> 17:51:27 UTC 2018 (28574e6) x86_64 x86_64 x86_64 GNU/Linux > >>>> btrfs --version > >>>> btrfs-progs v4.15 > >>> > >>> First I'd suggest to update to the latest btrfs progs. Then just run > >>> btrfs check --readonly --mode lowmem /path/to/device and paste the > >>> output. This won't do any changes to your filesystem but will give a > >>> better idea of what the corruption might be. > >> > >> Yep, that's pretty much recommended. > >> > >> On the other hand this kernel warning message just means exactly > what it > >> says. > >> One of your DIR_ITEM has incorrect hash. > >> > >> IIRC this is an old bug in kernel, not sure when it get fixed but it > >> should definitely get fixed now. > >> > >> If btrfs check --readonly shows *NO OTHER* bug, I have the check-next > >> branch which could fix it. > >> > >> But please keep in mind, don't run btrfs check --repair right now. > >> > >> Thanks, > >> Qu > >> > >>> > >>>> > >>>> tnx in advance > >>>> >
Attachment:
signature.asc
Description: OpenPGP digital signature
