--- ./f_badprimary/expect.1	2007-06-30 12:58:35.000000000 +0000
+++ f_badprimary.1.log	2008-01-12 21:18:31.000000000 +0000
@@ -1,27 +1 @@
-Filesystem did not have a UUID; generating one.
-
-Pass 1: Checking inodes, blocks, and sizes
-The primary superblock (1) is on the bad block list.
-
-If the block is really bad, the filesystem can not be fixed.
-You can remove this block from the bad block list and hope
-that the block is really OK.  But there are no guarantees.
-
-Clear? yes
-
-Block 2 in the primary group descriptors is on the bad block list
-
-If the block is really bad, the filesystem can not be fixed.
-You can remove this block from the bad block list and hope
-that the block is really OK.  But there are no guarantees.
-
-Clear? yes
-
-Pass 2: Checking directory structure
-Pass 3: Checking directory connectivity
-Pass 4: Checking reference counts
-Pass 5: Checking group summary information
-
-test_filesys: ***** FILE SYSTEM WAS MODIFIED *****
-test_filesys: 11/32 files (0.0% non-contiguous), 22/100 blocks
-Exit status is 1
+Exit status is 127
--- ./f_badprimary/expect.2	2007-06-30 12:58:35.000000000 +0000
+++ f_badprimary.2.log	2008-01-12 21:18:33.000000000 +0000
@@ -1,7 +1 @@
-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/32 files (0.0% non-contiguous), 22/100 blocks
-Exit status is 0
+Exit status is 127