TODO

   1 User request:
   2
   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
   7      by hand :-
   8
   9 ------------------------------------------
  10
  11 Add a "answer Yes always to this class of question" response.
  12
  13 ----------------------------------
  14
  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.
  18
  19 -----------------------------------
  20
  21 Put code into e2fsck to support imagic inodes....
  22
  23 ---------------------------------
  24 Date: Mon, 08 Mar 1999 21:46:14 +0100
  25 From: Sergio Polini <s.polini@mclink.it>
  26
  27
  28 I'm reading the sorce code of e2fsck 1.14.
  29 In pass2.c, lines 352-357, I read:
  30
  31 if ((dirent->name_len & 0xFF) > EXT2_NAME_LEN) {
  32         if (fix_problem(ctx, PR_2_FILENAME_LONG, &cd->pctx)) {
  33                 dirent->name_len = EXT2_NAME_LEN;
  34                 dir_modified++;
  35         }
  36 }
  37
  38 I think that I'll never see any messages about too long filenames,
  39 because "whatever & 0xFF" can never be "> 0xFF".
  40 Am I wrong?
  41 --------------------------------------
  42
  43 Add chmod command to debugfs.
  44