[Ocfs2-users] Unable to fix corrupt directories with fsck.ocfs2

[Sunil Mushran]

Did you run fsck with the force flag?
$ fsck.ocfs2 -f /dev/sdX

By default, fsck only replays the journals.

Paul Taylor wrote:
> Hi
>
> errors like the one listed below have been coming through in our logs on 
> a daily basis. We tried to run fsck.ocfs2 over the file system bet it 
> thinks that it is clean. We are wondering if there is another tool 
> available or process to follow to resolve the corruption.
>
> OS: Linux lp-bbprd1-rh4v 2.6.9-78.0.22.ELsmp
> ocfs2.1.2.9-1
>
> May 14 10:03:14 lp-bbprd1-rh4v kernel: (20690,1):ocfs2_lookup:183 ERROR: 
> Unable to create inode 75385485
> May 14 10:03:43 lp-bbprd1-rh4v kernel: 
> (14213,0):ocfs2_check_dir_entry:1727 ERROR: bad entry in directory 
> #76004924: rec_len is smaller than minimal - offset=0, inode=0, 
> rec_len=0, name_len=0
> May 14 10:03:43 lp-bbprd1-rh4v kernel: 
> (14213,0):ocfs2_check_dir_entry:1727 ERROR: bad entry in directory 
> #76004924: rec_len is smaller than minimal - offset=0, inode=0, 
> rec_len=0, name_len=0
> May 14 10:03:43 lp-bbprd1-rh4v kernel: (14213,0):ocfs2_empty_dir:305 
> ERROR: bad directory (dir #76004924) - no `.' or `..'
> May 14 10:03:43 lp-bbprd1-rh4v kernel: (14213,0):ocfs2_empty_dir:305 
> ERROR: bad directory (dir #76004924) - no `.' or `..'
>