Re: btrfs corruption: invalid mode: has 00 expect valid S_IF* bit(s)

[Qu Wenruo <quwenruo.btrfs@gmx.com>]

[-- Attachment #1.1: Type: text/plain, Size: 2351 bytes --]



On 2019/8/15 下午4:39, Jim Geo wrote:
> Hello,
> 
> my  /home folder is on a single device btrfs partition.
> When I ls a directory, I get these messages on ls:
> ls: cannot access 'file1' : Input/output error
> ls: cannot access 'file2' : Input/output error
> ls: cannot access 'file3' : Input/output error
> 
> and dmesg says:
> [31209.938486] BTRFS critical (device sdd1): corrupt leaf: root=5
> block=859701248 slot=93 ino=5830829, invalid mode: has 00 expect valid
> S_IF* bit(s)

Please provide the dump of that tree blocks.

# btrfs ins dump-tree -b 859701248 /dev/sdd1

It looks like that tree block has something wrong with it.
Thus kernel reject to accept the data.

[...]
> 
> I scrubbed the filesystem but no errors were detected/fixed.

Scrub mostly only verify checksum, doesn't care about the data in the
tree blocks.

> 
> btrfs scrub status /home:
> scrub status for myuuid
>         scrub started at Thu Aug 15 02:24:42 2019 and finished after 03:55:12
>         total bytes scrubbed: 2.05TiB with 0 errors
> 
>  uname -a:
> Linux gentoo 5.2.8-ck #1 SMP PREEMPT Wed Aug 14 20:44:33 EEST 2019
> x86_64 Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz GenuineIntel GNU/Linux
> 
> btrfs --version:
> btrfs-progs v4.19
> 
> btrfs fi show:
> Label: 'home_btrfs'  uuid:-------
>         Total devices 1 FS bytes used 2.04TiB
>         devid    1 size 2.13TiB used 2.13TiB path /dev/sdd1
> 
> btrfs fi df /home:
> Data, single: total=2.12TiB, used=2.04TiB
> System, DUP: total=64.00MiB, used=256.00KiB
> Metadata, DUP: total=7.00GiB, used=4.48GiB
> GlobalReserve, single: total=512.00MiB, used=0.00B
> 
> btrfs device stats /home:
> [/dev/sdd1].write_io_errs    4
> [/dev/sdd1].read_io_errs     3
> [/dev/sdd1].flush_io_errs    0
> [/dev/sdd1].corruption_errs  0
> [/dev/sdd1].generation_errs  0
> 
> mount options:
> /dev/sdd1 on /home type btrfs
> (rw,relatime,space_cache,autodefrag,subvolid=5,subvol=/)
> 
> How can I fix this corruption? How can I detect if more
> files/directories are affected?

Affected inode number is 5830829. But I need to above mentioned dump to
make sure if it's not a false alert.

If it's truely corrupted by whatever the reason, you'd
better check your memory, as it looks like a bit flip.

Thanks,
Qu
> 
> Kind Regards,
> Jim
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]