Theodore Ts'o | c461e16 | 1999-01-12 23:40:01 +0000 | [diff] [blame] | 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 |
Theodore Ts'o | e2e69ba | 1999-06-18 01:13:31 +0000 | [diff] [blame] | 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 | |
Theodore Ts'o | e2e69ba | 1999-06-18 01:13:31 +0000 | [diff] [blame] | 19 | --------------------------------- |
Theodore Ts'o | e2e69ba | 1999-06-18 01:13:31 +0000 | [diff] [blame] | 20 | Date: Mon, 08 Mar 1999 21:46:14 +0100 |
| 21 | From: Sergio Polini <s.polini@mclink.it> |
| 22 | |
| 23 | |
| 24 | I'm reading the sorce code of e2fsck 1.14. |
| 25 | In pass2.c, lines 352-357, I read: |
| 26 | |
| 27 | if ((dirent->name_len & 0xFF) > EXT2_NAME_LEN) { |
| 28 | if (fix_problem(ctx, PR_2_FILENAME_LONG, &cd->pctx)) { |
| 29 | dirent->name_len = EXT2_NAME_LEN; |
| 30 | dir_modified++; |
| 31 | } |
| 32 | } |
| 33 | |
| 34 | I think that I'll never see any messages about too long filenames, |
| 35 | because "whatever & 0xFF" can never be "> 0xFF". |
| 36 | Am I wrong? |
| 37 | -------------------------------------- |
| 38 | |
Theodore Ts'o | e2a99be | 1999-07-19 15:48:08 +0000 | [diff] [blame] | 39 | Add chmod command to debugfs. |
Theodore Ts'o | e2e69ba | 1999-06-18 01:13:31 +0000 | [diff] [blame] | 40 | |
Theodore Ts'o | 8a31ffe | 1999-10-23 03:33:15 +0000 | [diff] [blame] | 41 | ------------------------------------------ |
| 42 | |
| 43 | fix up get_backup_sb, so that it doesn't choose something bogus if |
| 44 | fs->super->.... is ridiculous |
| 45 | |
Theodore Ts'o | 24ded09 | 1999-11-10 15:56:16 +0000 | [diff] [blame] | 46 | ---------------------------------- |
| 47 | |
| 48 | Maybe a bug in debugfs v.1.14: |
| 49 | if a file has more than one hardlink, only the first filename is shown when |
| 50 | using command |
| 51 | ncheck <inode> |
| 52 | |
| 53 | ------------------------------------ |
Theodore Ts'o | fdbba5c | 2000-02-08 23:16:51 +0000 | [diff] [blame] | 54 | |
| 55 | Add a filesystem creation date to the superblock |
| 56 | |
| 57 | ----------------------------------- |
| 58 | Date: Tue, 18 Jan 2000 17:54:53 -0800 (PST) |
| 59 | From: Alan Blanchard <alan@abraxas.to> |
| 60 | To: tytso@MIT.EDU |
| 61 | Subject: DEBUGFS - thanks and a feature idea |
| 62 | Content-Type: TEXT/PLAIN; charset=US-ASCII |
| 63 | |
| 64 | Theodore: |
| 65 | |
| 66 | First, let me thank you for writing debugfs. Recently, my Linux box |
| 67 | (RH 6.0, 400 MHz PIII, on a DSL line) was hacked into. The intruder did |
| 68 | an "rm -Rf" on a 34 GB drive with about 5GB of data on it. I was able to |
| 69 | restore essentially the entire thing with debugfs and a bit of C code and Perl. |
| 70 | Actually, I could have done the entire thing with debugfs and Perl, but I |
| 71 | thought it would be too slow. |
| 72 | |
| 73 | During this exercise, I noticed that one small feature was lacking that would |
| 74 | have made my job a bit easier. The length of a deleted directory is |
| 75 | reported as 0, hence debugfs won't dump the contents of the directory to a |
| 76 | file using the "dump" command. The only thing that saved me was that the |
| 77 | list of disk blocks is not zeroed out. I was able to dump the contents of the |
| 78 | directories by using debugfs to get the relevant block numbers, then |
| 79 | using dd to get the actual data. |
| 80 | |
| 81 | If debugfs had a feature where it ignored the size of a directory reported by |
| 82 | the inode and instead just dumped all the blocks, it would have facilited |
| 83 | things a bit. This seems like a very easy feature to add. |
| 84 | |
| 85 | Again, thanks for writing debugfs (and all the other Linux stuff you've written!). |
| 86 | |
| 87 | Cheers, |
| 88 | Alan Blanchard |
| 89 | alan@abraxas.to |
| 90 | |
| 91 | |
| 92 | ------------------------------------------------------------------- |
| 93 | |
| 94 | Date: Fri, 21 Jan 2000 14:07:12 -0800 |
| 95 | From: "H. Peter Anvin" <hpa@www.transmeta.com> |
| 96 | Subject: mkfs -cc and fsck -c |
| 97 | |
| 98 | a) An option to mkfs to run badblocks in read/write mode. The |
| 99 | filesystem is blank, so this is the perfect time to run the read/write |
| 100 | test. |
| 101 | |
| 102 | b) An option to mkfs to zero the partition. Yes, it can be done with |
| 103 | dd, but it would be a nicer way of doing it. |
| 104 | |
Theodore Ts'o | 1917875 | 2000-02-11 15:55:07 +0000 | [diff] [blame] | 105 | ------------------------------------------------------------------ |
| 106 | |
| 107 | Add support for in ext2fs_block_iterate() for a returning the |
| 108 | compressed flag blocks to block_iterate. Change default to not return |
| 109 | EXT2_COMPRESSED_BLKADDR. Change e2fsck to pass this flag in. |
| 110 | |
| 111 | (The old compression patches did this by default all the time, which |
| 112 | is bad, since it meant e2fsck never saw the EXT2_COMPRESSED_BLKADDR |
| 113 | flagword. |
| 114 | |
| 115 | ------------------------------------------------------------ |
| 116 | |
| 117 | E2fsck should offer to clear all the blocks in an indirect block, not |
| 118 | the entire inode, so there's better recovery for when an indirect |
| 119 | block gets trashed. |
| 120 | |
| 121 | |