I untarred a file with a lot (~5000) of small files (average length < 500 bytes)
and a lot of directories.
Then I `rm -rf'ed the untarred tree.
Just after that I untarred it again.
Then, while accessing these files, I got the following errors:
Oct 11 11:56:43 vvv kernel: EXT2-fs error (device 03:03): ext2_readdir: bad entry in directory #124959: directory entry across blocks - offset=0, inode=1635020660, rec_len=8300, name_len=2608
Oct 11 11:56:43 vvv kernel: EXT2-fs error (device 03:03): ext2_find_entry: bad entry in directory #124959: directory entry across blocks - offset=0, inode=1635020660, rec_len=8300, name_len=2608
Oct 11 11:56:58 vvv kernel: EXT2-fs error (device 03:03): ext2_readdir: bad entry in directory #124959: directory entry across blocks - offset=0, inode=1635020660, rec_len=8300, name_len=2608
Oct 11 11:56:58 vvv kernel: EXT2-fs error (device 03:03): ext2_find_entry: bad entry in directory #124959: directory entry across blocks - offset=0, inode=1635020660, rec_len=8300, name_len=2608
After that I sync'ed the file system and pressed reset, --- in order
to check the file system after a reboot.
Ext2fsck found lots of errors (like unpresence of `.' and `..' in a directory, unconnected inodes, etc.).
Also, I got a message like
WARNING: PROGRAMMING BUG IN E2FSCK!
OR SOME BONEHEAD (YOU) IS CHECKING A MOUNTED (LIVE) FILESYSTEM.
(the filesystem was, of course, mounted readonly). This may have happened because
I rebooted the system via hard reset?
I use e2fsprogs-1.10.
This seems to be a bug in the kernel.
With best regards, Vladimir.