fsck.ext4 -n exited with status code 4
e2fsck 1.47.0 (5-Feb-2023)
syzkaller contains a file system with errors, check forced.
Resize inode not valid.  Recreate? no

Pass 1: Checking inodes, blocks, and sizes
Inode 7 has illegal block(s).  Clear? no

Illegal block #2 (4278190080) in inode 7.  IGNORED.
Illegal block #5 (458752) in inode 7.  IGNORED.
Inode 7, i_blocks is 64, should be 128.  Fix? no

Inode 13 has corrupt extent header.  Clear inode? no

Inode 13, i_blocks is 64, should be 0.  Fix? no

Inode 14, i_blocks is 281470681743360, should be 0.  Fix? no

Inode 16, i_blocks is 7, should be 64.  Fix? no

Pass 2: Checking directory structure
i_faddr for inode 14 (.../file0/file1) is 4211081216, should be zero.
Clear? no

Extended attribute block for inode 14 (.../file0/file1) is invalid (281470681743360).
Clear? no

Entry 'file1' in .../file0 (12) has an incorrect filetype (was 7, should be 0).
Fix? no

First entry '^@' (inode=2) in directory inode 2 (...) should be '.'
Fix? no

Entry '^@' in ... (2) has illegal characters in its name.
Fix? no

Missing '..' in directory inode 2.
Fix? no

Pass 3: Checking directory connectivity
'..' in ... (2) is <The NULL inode> (0), should be ... (2).
Fix? no

Pass 4: Checking reference counts
Inode 2 ref count is 4, should be 3.  Fix? no

Pass 5: Checking group summary information
Block bitmap differences:  -80 -(112--496)
Fix? no

Free blocks count wrong for group #0 (150994969, counted=0).
Fix? no

Free blocks count wrong (400, counted=0).
Fix? no


syzkaller: ********** WARNING: Filesystem still has errors **********

syzkaller: 17/32 files (0.0% non-contiguous), 112/512 blocks