Actually, i was just guessing it's a lvm error.
When I searched, one hit suggested that fsck will fix it.
Anyway, from the message file:
Oct 11 18:13:20 hostname kernel: EXT3-fs error (device sda3): ext3_readdir:
bad entry in directory #2: inode out of bounds - offset=24, inode=11,
rec_len=20, name_len=10
find issue led to possible fsck bug ... in your filesystem driver.... I recommended they run fsck on the file systems to identify and fix any ...Free inodes count wrong ... (Fedora)
Re: find issue led to possible fsck bug ... I recommended they run fsck on the file systems to identify and fix any ... skipping journal recovery because doing a read-only filesystem...Free inodes count wrong ... (Fedora)
Re: Directory Size problem ... In any case, I expect fsck will simply note there is an inconsistency in the size/block count/allocation, check the actual allocations and correct the count. ... I'm not sure if just deleting it would fix it at this point, or if an fsck is required to fix it, but it would surely be safer to let fsck have a crack at it. ... Or, if I needed the mqueue directory, I would move the current one to a different name and make a new mqueue directory and leave the flukey one alone.... (Fedora)
Re: Getting signal 15 after boot ... > Freeing unused kernel memory:... Or unix ptty support.... Just fsck your fs and fix the problems notedd before ging any further. ... (comp.os.linux.setup)
LSM mirroring, another problem ... fsck the filesystem after the mirroring, I get a lot of errors, too many to ...fix this? ...fsck was OK until I attached the mirror. ... # disklabel -wr dsk3... (Tru64-UNIX-Managers)
