Datasheet

“main” (Installation and Administration) — 2004/6/25 — 13:29 — page 733 — #759

Manual Page of e2fsck

REPORTING BUGS

Almost any piece of software will have bugs. If you

manage to find a filesystem which causes e2fsck to crash,

or which e2fsck is unable to repair, please report it to

the author.

Please include as much information as possible in your bug

report. Ideally, include a complete transcript of the

e2fsck run, so I can see exactly what error messages are

displayed. If you have a writeable filesystem where the

transcript can be stored, the script(1) program is a handy

way to save the output of e2fsck to a file.

It is also useful to send the output of dumpe2fs(8). If a

specific inode or inodes seems to be giving e2fsck trou

ble, try running the debugfs(8) command and send the out

put of the stat(1u) command run on the relevant inode(s).

If the inode is a directory, the debugfs dump command will

allow you to extract the contents of the directory inode,

which can sent to me after being first run through uuen

code(1).

Always include the full version string which e2fsck dis

plays when it is run, so I know which version you are run

ning.

AUTHOR

This version of e2fsck was written by Theodore Ts’o

<tytso@mit.edu>.