проверьте файловую систему Linux ext2 / ext3 / ext4 (check a Linux ext2/ext3/ext4 file system)
Сообщение об ошибках (Reporting bugs)
Almost any piece of software will have bugs. If you manage to
find a file system 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.
(Make sure the messages printed by e2fsck are in English; if your
system has been configured so that e2fsck's messages have been
translated into another language, please set the the LC_ALL
environment variable to C so that the transcript of e2fsck's
output will be useful to me.) If you have a writable file system
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 trouble, try
running the debugfs(8) command and send the output 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 uuencode(1). The most useful data you can send
to help reproduce the bug is a compressed raw image dump of the
file system, generated using e2image(8). See the e2image(8) man
page for more details.
Always include the full version string which e2fsck displays when
it is run, so I know which version you are running.
