3 BTW: Could you please add some sort of deleted and possibly corrupted file
4 and inode list to e2fsck report. There should be filenames deleted
5 from directory inodes, files with duplicate blocks e.t.c.
6 It's pretty annoying to filter this information from e2fsck output
9 ------------------------------------------
11 Add a "answer Yes always to this class of question" response.
13 ----------------------------------
15 ext2fs_flush() should return a different error message for primary
16 versus backup superblock flushing, so that mke2fs can print an
17 appropriate error message.
19 -----------------------------------
21 Put code into e2fsck to support imagic inodes....
23 ---------------------------------
25 Deal with the case where /lost+found isn't a directory....
28 --------------------------------------
29 Date: Mon, 08 Mar 1999 21:46:14 +0100
30 From: Sergio Polini <s.polini@mclink.it>
33 I'm reading the sorce code of e2fsck 1.14.
34 In pass2.c, lines 352-357, I read:
36 if ((dirent->name_len & 0xFF) > EXT2_NAME_LEN) {
37 if (fix_problem(ctx, PR_2_FILENAME_LONG, &cd->pctx)) {
38 dirent->name_len = EXT2_NAME_LEN;
43 I think that I'll never see any messages about too long filenames,
44 because "whatever & 0xFF" can never be "> 0xFF".
46 --------------------------------------
48 debugfs --- ls of a corrupt directory (or a non-directory inode) with
49 inconsistent lengths can cause it to core dump! Should fix to make it
52 -------------------------------------