1 Need to process the bad block inode *before* doing the inode scan.
3 Also check to see if the first block of the inode table is not on the
4 bad block scan, and fix that. We need to check for an inaccurate
5 blocks, and fix them before we start doing anything else with the
8 ---------------------------------------------------
11 BTW: Could you please add some sort of deleted and possibly corrupted file
12 and inode list to e2fsck report. There should be filenames deleted
13 from directory inodes, files with duplicate blocks e.t.c.
14 It's pretty annoying to filter this information from e2fsck output
17 ------------------------------------------
19 Add a "answer Yes always to this class of question" response.
21 ----------------------------------
23 ext2fs_flush() should return a different error message for primary
24 versus backup superblock flushing, so that mke2fs can print an
25 appropriate error message.
27 ---------------------------------
28 Date: Mon, 08 Mar 1999 21:46:14 +0100
29 From: Sergio Polini <s.polini@mclink.it>
32 I'm reading the sorce code of e2fsck 1.14.
33 In pass2.c, lines 352-357, I read:
35 if ((dirent->name_len & 0xFF) > EXT2_NAME_LEN) {
36 if (fix_problem(ctx, PR_2_FILENAME_LONG, &cd->pctx)) {
37 dirent->name_len = EXT2_NAME_LEN;
42 I think that I'll never see any messages about too long filenames,
43 because "whatever & 0xFF" can never be "> 0xFF".
45 --------------------------------------
47 Add chmod command to debugfs.
49 ------------------------------------------
51 Maybe a bug in debugfs v.1.14:
52 if a file has more than one hardlink, only the first filename is shown when
56 ------------------------------------
58 Add a filesystem creation date to the superblock
60 -----------------------------------
61 Date: Tue, 18 Jan 2000 17:54:53 -0800 (PST)
62 From: Alan Blanchard <alan@abraxas.to>
64 Subject: DEBUGFS - thanks and a feature idea
65 Content-Type: TEXT/PLAIN; charset=US-ASCII
69 First, let me thank you for writing debugfs. Recently, my Linux box
70 (RH 6.0, 400 MHz PIII, on a DSL line) was hacked into. The intruder did
71 an "rm -Rf" on a 34 GB drive with about 5GB of data on it. I was able to
72 restore essentially the entire thing with debugfs and a bit of C code and Perl.
73 Actually, I could have done the entire thing with debugfs and Perl, but I
74 thought it would be too slow.
76 During this exercise, I noticed that one small feature was lacking that would
77 have made my job a bit easier. The length of a deleted directory is
78 reported as 0, hence debugfs won't dump the contents of the directory to a
79 file using the "dump" command. The only thing that saved me was that the
80 list of disk blocks is not zeroed out. I was able to dump the contents of the
81 directories by using debugfs to get the relevant block numbers, then
82 using dd to get the actual data.
84 If debugfs had a feature where it ignored the size of a directory reported by
85 the inode and instead just dumped all the blocks, it would have facilited
86 things a bit. This seems like a very easy feature to add.
88 Again, thanks for writing debugfs (and all the other Linux stuff you've written!).
95 -------------------------------------------------------------------
97 Date: Fri, 21 Jan 2000 14:07:12 -0800
98 From: "H. Peter Anvin" <hpa@www.transmeta.com>
99 Subject: mkfs -cc and fsck -c
101 b) An option to mkfs to zero the partition. Yes, it can be done with
102 dd, but it would be a nicer way of doing it.
104 ------------------------------------------------------------------
106 Add support for in ext2fs_block_iterate() for a returning the
107 compressed flag blocks to block_iterate. Change default to not return
108 EXT2_COMPRESSED_BLKADDR. Change e2fsck to pass this flag in.
110 (The old compression patches did this by default all the time, which
111 is bad, since it meant e2fsck never saw the EXT2_COMPRESSED_BLKADDR
114 ------------------------------------------------------------
116 E2fsck should offer to clear all the blocks in an indirect block, not
117 the entire inode, so there's better recovery for when an indirect
121 -------------------------------------------------------------
123 From: Yann Dirson - LOGATIQUE <Yann.Dirson@France.Sun.COM>
124 Date: Thu, 2 Mar 2000 13:52:13 +0100 (MET)
126 During my experiments on the broken system, I noticed the following in
127 the badblocks program (which I'm aware is not designed for IDE drives)
128 - I'd probably have already fixed them if my home system was up :(
130 * the syntax summary documents 2nd arg as blocks_count, which should
131 probably read something like end_count.
133 * testing past end of device is not detected, and lists those blocks
134 as bad, whereas they simply do not exist.
137 I think I'll probably add a "max count" option to findsuper(8), so
138 that I do not have to wait for the whole disk to be scanned when the
139 system had to be launched with "init=/bin/sh", in which case Ctrl-[CZ]
140 and friends appear to be absolutely ignored.
143 Somewhat unrelated, I just noticed the
144 http://web.mit.edu/tytso/www/linux/ext2.html could be updated:
146 - could mention SGI xfs (http://oss.sgi.com/projects/xfs/ - they just
147 release 0.03 snapshot)
149 ----------------------------------------------------------------
151 Return-Path: <tytso@MIT.EDU>
152 Date: Thu, 10 Feb 2000 13:20:14 -0500
153 From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
154 To: R.E.Wolff@BitWizard.nl
155 In-Reply-To: Rogier Wolff's message of Thu, 10 Feb 2000 08:46:30 +0100 (MET),
156 <200002100746.IAA24573@cave.bitwizard.nl>
157 Subject: Re: e2fsck request for enhancement.
158 Phone: (781) 391-3464
160 Date: Thu, 10 Feb 2000 08:46:30 +0100 (MET)
161 From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
163 Lately, while trying to recover a broken disk, my system froze (twice,
164 until I tried something else) while copying the disk.
166 So I had a file of about 50Mb that was growing frantically at the
169 e2fsck, then finds an indirect block that is completely bogus. It
170 starts by asking me if it's ok to clear a few of the referenced
171 blocks. I say yes. Then it comes to the conclusion:
173 too many invalid blocks. Clear inode?
175 and then I get the option to delete the whole file. Not to truncate
176 the file to a "working" size.
179 I'd MUCH rather have e2fsck say something like:
181 inode 1234 references an invalid block 134345454. Hmm.
182 inode 1234 references 567 out of 50176 invalid blocks,
183 all near the end. Truncate file to 49152 blocks?
185 Here you can see that of the 1024 blocks near the end of the file,
186 only 567 were detected as invalid. However now 48Mb of the file will
187 be recovered, instead of thrown away.
189 That's a good point. Actually, the right thing is for e2fsck to offer
190 to clear all of the bad blocks in a particular indirect block. I don't
191 know how hard it would be to do that, but I'll put it on my e2fsprogs
196 ---------------------------------------------------------------
197 From e2fsprogs Debian TODO file as of 1.10-13.
199 * Maybe make -dbg packages. Look at how others do it.
201 ---------------------------------------------------------------
203 Add --lba option to debian icheck command, and have ways of making it
204 easier to translate LBA to filesystem block numbers.
206 -------------------------------------------------------
208 Move creator_os string parsing and unparsing from mke2fs and e2p/ls.c
209 to a centralized e2p library function.