6.21 E2fsprogs-1.41.10 101 Tests failured -make check

Bill Brown wubrown at gmail.com
Tue May 4 17:36:22 PDT 2010

Chris, thanks for the prompt response.  I have spent a good chunk of 
time looking at the tests\*.log & .failed files.  If like the DOS world, 
anything but exit status 0 is an error, I suspect the Exit status 127's 
are failures.  Here is a snippet from r_move_itable.failed that points 
to "super-block" issues:
root:/sources/e2fsprogs-1.41.10/build/tests# more r_move_itable.failed
--- ../../tests/r_move_itable/expect    2009-08-13 01:39:58.000000000 +0000
+++ r_move_itable.log    2010-05-05 15:22:33.000000000 +0000
@@ -1,2622 +1,28 @@
  mke2fs -q -F -o Linux -b 1024 -g 256 test.img 1024
  resize2fs -p test.img 10000
-Resizing the filesystem on ./test.img to 10000 (1k) blocks.
-Begin pass 1 (max = 35)
-The filesystem on ./test.img is now 9985 blocks long.
-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/1248 files (0.0% non-contiguous), 1281/9985 blocks
-Exit status is 0
+../resize/resize2fs: Bad magic number in super-block while trying to 
open ./tes
+Couldn't find valid filesystem superblock.
+Exit status is 127
Looking at the test script if I understand it correctly,  it creates a 
test file system, resizes it and then checks the resulting fs.  It looks 
like the fsck completes OK it is not clear at what open of ./test.img is 
resulting in the magic number error.  At this point I do not have an 
/etc/fstab file in chroot environment.  There is an empty /etc/mtab 
file.  I do have the libmagic link libraries in /usr/lib Does this point 
anyone to the problem causing the 101 e2fsprogs test failures?

Again thanks for any clarity...
On 5/4/2010 3:57 PM, Chris Staub wrote:
> On 05/04/2010 06:28 PM, Bill Brown wrote:
>> I have spend a good day trying to figure out the cause of all tests
>> failing except for the first two and last two when issuing the 'make
>> check' command;
>> I am using the 6.6 version of the LFS book.  Running on Ubuntu desktop
>> 9.10.  Which in turn is a virtual machine on VMware ESXi 4.0 free.  I am
>> new to Linux development but have considerable console programming
>> experience in C, C++, Java and earlier languages.  I am wanting to begin
>> an open source development project to run on Linux so looking to broaden
>> my foundation via this LFS process.
>> Thanks for any insights...  Bill
> That many failing tests likely indicates some kind of serious problems,
> though the output given doesn't really provide any info outside of
> saying that tests failed. There are likely clues in the log files for
> each test - check in the "tests" directory (inside the "build" dir) for
> .log files - inspect the log for each test and see if any provide useful
> information.

More information about the lfs-support mailing list