New regression test which contains a corrupt ind. block in the journal inode

Signed-off-by: Kalpak Shah <kalpak@clusterfs.com>
Signed-off-by: Andreas Dilger <adilger@clusterfs.com>

tests/ChangeLog

@@ -1,3 +1,8 @@
+2007-06-21  Theodore Tso  <tytso@mit.edu>
+
+	* f_badjour_indblks: New test case which checks if a corrupted
+		indirect block in the journal inode will get caught.
+
 2007-04-10  Theodore Tso  <tytso@mit.edu>
 
 	* f_dup4: New test cases which tests a bugfix in e2fsck where if an

tests/f_badjour_indblks/expect.1

@@ -0,0 +1,33 @@
+Superblock has an invalid ext3 journal (inode 8).
+Clear? yes
+
+*** ext3 journal has been deleted - filesystem is now ext2 only ***
+
+Adding dirhash hint to filesystem.
+
+Pass 1: Checking inodes, blocks, and sizes
+Journal inode is not in use, but contains data.  Clear? yes
+
+Pass 2: Checking directory structure
+Pass 3: Checking directory connectivity
+Pass 4: Checking reference counts
+Pass 5: Checking group summary information
+Block bitmap differences:  -(82--1111)
+Fix? yes
+
+Free blocks count wrong for group #0 (7080, counted=8110).
+Fix? yes
+
+Free blocks count wrong (7080, counted=8110).
+Fix? yes
+
+Recreate journal to make the filesystem ext3 again?
+Fix? yes
+
+Creating journal (1024 blocks):  Done.
+
+*** journal has been re-created - filesystem is now ext3 again ***
+
+test_filesys: ***** FILE SYSTEM WAS MODIFIED *****
+test_filesys: 11/256 files (9.1% non-contiguous), 1112/8192 blocks
+Exit status is 1

tests/f_badjour_indblks/expect.2

@@ -0,0 +1,7 @@
+Pass 1: Checking inodes, blocks, and sizes
+Pass 2: Checking directory structure
+Pass 3: Checking directory connectivity
+Pass 4: Checking reference counts
+Pass 5: Checking group summary information
+test_filesys: 11/256 files (9.1% non-contiguous), 1112/8192 blocks
+Exit status is 0

tests/f_badjour_indblks/name

@@ -0,0 +1 @@
+corruption in journal inode's indirect blocks