[Ocfs2-users] enabling indexed-dirs fails due to corrupted directory entry

David Sobon dsobon at gmail.com
Tue May 8 11:03:16 PDT 2012


During migration from OCFS2 1.4 to 1.6, I experienced a few issues.

Enabling "indexed-dirs" resulted in the following:
tunefs.ocfs2: Install directory trailer failed while enable indexed-dirs
tunefs.ocfs2: Install directory trailer failed while building indexed trees

"fsck.ocfs2 -f" resolved many errors (the first one was related to
"duplicate clusters"), but still could not solve this one:

"[DIRENT_LENGTH] Directory inode 1207004 corrupted in logical block 6
physical block 16777216 offset 0. Attempt to repair this block's
directory entries? <y> y"

I do know which directory the inode it belongs to (it has quite a few
files in it! and I do have backups) by utilising this command:
debugfs.ocfs2 -R "findpath <1207004>" /dev/drbd0

Accessing the directory ("ls -la") results in the following kernel message:
"(ls,23225,0):ocfs2_check_dir_entry:340 ERROR: bad entry in directory
#1207004: rec_len % 4 != 0 - offset=0, inode=55346345689935,
rec_len=10333, name_len=126"

What options do I have to be able to resolve this problem?

Any assistance is appreciated.

David.



More information about the Ocfs2-users mailing list