From 464df1d5e5ab1322e2dd0a7796939fff1aeefa9a Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sun, 7 Apr 2024 17:49:25 +0200 Subject: Adding upstream version 1.47.0. Signed-off-by: Daniel Baumann --- tests/f_boundscheck/expect.1 | 25 +++++++++++++++++++++++++ tests/f_boundscheck/expect.2 | 25 +++++++++++++++++++++++++ tests/f_boundscheck/image.bz2 | Bin 0 -> 986 bytes tests/f_boundscheck/name | 1 + tests/f_boundscheck/script | 31 +++++++++++++++++++++++++++++++ 5 files changed, 82 insertions(+) create mode 100644 tests/f_boundscheck/expect.1 create mode 100644 tests/f_boundscheck/expect.2 create mode 100644 tests/f_boundscheck/image.bz2 create mode 100644 tests/f_boundscheck/name create mode 100755 tests/f_boundscheck/script (limited to 'tests/f_boundscheck') diff --git a/tests/f_boundscheck/expect.1 b/tests/f_boundscheck/expect.1 new file mode 100644 index 0000000..c2170b8 --- /dev/null +++ b/tests/f_boundscheck/expect.1 @@ -0,0 +1,25 @@ +ext2fs_check_desc: Corrupt group descriptor: bad block for inode table +../e2fsck/e2fsck: Group descriptors look bad... trying backup blocks... +../e2fsck/e2fsck: Bad magic number in super-block while using the backup blocks../e2fsck/e2fsck: going back to original superblock +Note: if several inode or block bitmap blocks or part +of the inode table require relocation, you may wish to try +running e2fsck with the '-b 8193' option first. The problem +may lie only with the primary block group descriptors, and +the backup block group descriptors may be OK. + +Inode table for group 1 is not in group. (block 4294967295) +WARNING: SEVERE DATA LOSS POSSIBLE. +Relocate? yes + +One or more block group descriptor checksums are invalid. Fix? yes + +Group descriptor 1 checksum is 0x6ea2, should be 0x7edd. FIXED. +Pass 1: Checking inodes, blocks, and sizes +Error allocating 256 contiguous block(s) in block group 1 for inode table: Could not allocate block in ext2 filesystem +e2fsck: aborted + +test_filesys: ***** FILE SYSTEM WAS MODIFIED ***** + +test_filesys: ********** WARNING: Filesystem still has errors ********** + +Exit status is 0 diff --git a/tests/f_boundscheck/expect.2 b/tests/f_boundscheck/expect.2 new file mode 100644 index 0000000..c2170b8 --- /dev/null +++ b/tests/f_boundscheck/expect.2 @@ -0,0 +1,25 @@ +ext2fs_check_desc: Corrupt group descriptor: bad block for inode table +../e2fsck/e2fsck: Group descriptors look bad... trying backup blocks... +../e2fsck/e2fsck: Bad magic number in super-block while using the backup blocks../e2fsck/e2fsck: going back to original superblock +Note: if several inode or block bitmap blocks or part +of the inode table require relocation, you may wish to try +running e2fsck with the '-b 8193' option first. The problem +may lie only with the primary block group descriptors, and +the backup block group descriptors may be OK. + +Inode table for group 1 is not in group. (block 4294967295) +WARNING: SEVERE DATA LOSS POSSIBLE. +Relocate? yes + +One or more block group descriptor checksums are invalid. Fix? yes + +Group descriptor 1 checksum is 0x6ea2, should be 0x7edd. FIXED. +Pass 1: Checking inodes, blocks, and sizes +Error allocating 256 contiguous block(s) in block group 1 for inode table: Could not allocate block in ext2 filesystem +e2fsck: aborted + +test_filesys: ***** FILE SYSTEM WAS MODIFIED ***** + +test_filesys: ********** WARNING: Filesystem still has errors ********** + +Exit status is 0 diff --git a/tests/f_boundscheck/image.bz2 b/tests/f_boundscheck/image.bz2 new file mode 100644 index 0000000..098d02e Binary files /dev/null and b/tests/f_boundscheck/image.bz2 differ diff --git a/tests/f_boundscheck/name b/tests/f_boundscheck/name new file mode 100644 index 0000000..7d71be5 --- /dev/null +++ b/tests/f_boundscheck/name @@ -0,0 +1 @@ +infinite loop when finding table free space diff --git a/tests/f_boundscheck/script b/tests/f_boundscheck/script new file mode 100755 index 0000000..7a07265 --- /dev/null +++ b/tests/f_boundscheck/script @@ -0,0 +1,31 @@ +#!/bin/bash + +FSCK_OPT=-fy +IMAGE=$test_dir/image.bz2 + +bzip2 -d < $IMAGE > $TMPFILE +#e2label $TMPFILE test_filesys + +# Run fsck to fix things? +EXP1=$test_dir/expect.1 +OUT1=$test_name.1.log + +$FSCK $FSCK_OPT $TMPFILE 2>&1 | head -n 1000 | tail -n +2 > $OUT1 +echo "Exit status is $?" >> $OUT1 + +# Run a second time +EXP2=$test_dir/expect.2 +OUT2=$test_name.2.log + +$FSCK $FSCK_OPT $TMPFILE 2>&1 | head -n 1000 | tail -n +2 > $OUT2 +echo "Exit status is $?" >> $OUT2 + +# Figure out what happened +if cmp -s $EXP1 $OUT1 && cmp -s $EXP2 $OUT2; then + echo "$test_name: $test_description: ok" + touch $test_name.ok +else + echo "$test_name: $test_description: failed" + diff -u $EXP1 $OUT1 >> $test_name.failed + diff -u $EXP2 $OUT2 >> $test_name.failed +fi -- cgit v1.2.3