https://bugzilla.kernel.org/show_bug.cgi?id=207165 Bug ID: 207165 Summary: Persistent ext4_search_dir: bad entry in directory: directory entry too close to block end Product: File System Version: 2.5 Kernel Version: 5.5.16 Hardware: Intel OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: ext4 Assignee: fs_ext4@xxxxxxxxxxxxxxxxxxxx Reporter: el@xxxxxxxxx Regression: No Since 5.5 I started getting persistent hits at the check added in 109ba779d6cca (ext4: check for directory entries too close to block end). It is 100% reproducible when running docker containers on overlayfs2. Here's an example log entry: kernel: EXT4-fs error (device dm-0): ext4_search_dir:1395: inode #28320400: block 113246792: comm dockerd: bad entry in directory: directory entry too close to block end - offset=0, inode=28320403, rec_len=32, name_len=8, size=4096 dockerd[5315]: time="2020-04-08T11:03:35.148433258-07:00" level=error msg="Error removing mounted layer c520f6ce1d0b493e51aa9cdaea2240c6f65f104c3da8fb9767999dc526086f85: unlinkat /var/lib/docker/overlay2/01c0c02ee4841227fefe595eeef8912fee32bc2b63a2264cb513f924e6366950/diff/tmp/apt-key-gpghome.TauCtRwzyD: directory not empty" To clarify, this error happened elsewhere as well, so this doesn't seem to be overlayfs2-specific. At first I thought that my filesystem was borked somehow, so I went so far as to reformat the partition, but that didn't help. -- You are receiving this mail because: You are watching the assignee of the bug.
