Adding upstream version 1.47.0.upstream/1.47.0upstream

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

4 files changed, 20 insertions, 0 deletions

diff --git a/tests/f_crashdisk/expect.1 b/tests/f_crashdisk/expect.1
new file mode 100644
index 0000000..6898030
--- /dev/null
+++ b/tests/f_crashdisk/expect.1
@@ -0,0 +1,17 @@
+ext2fs_open2: The ext2 superblock is corrupt
+../e2fsck/e2fsck: Superblock invalid, trying backup blocks...
+../e2fsck/e2fsck: The ext2 superblock is corrupt while trying to open test.img
+../e2fsck/e2fsck: Trying to load superblock despite errors...
+ext2fs_open2: The ext2 superblock is corrupt
+../e2fsck/e2fsck: Superblock invalid, trying backup blocks...
+../e2fsck/e2fsck: The ext2 superblock is corrupt while trying to open test.img
+
+The superblock could not be read or does not describe a valid ext2/ext3/ext4
+filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
+filesystem (and not swap or ufs or something else), then the superblock
+is corrupt, and you might try running e2fsck with an alternate superblock:
+    e2fsck -b 8193 <device>
+ or
+    e2fsck -b 32768 <device>
+
+Exit status is 8
diff --git a/tests/f_crashdisk/image.gz b/tests/f_crashdisk/image.gz
new file mode 100644
index 0000000..060e7a0
--- /dev/null
+++ b/tests/f_crashdisk/image.gz
diff --git a/tests/f_crashdisk/name b/tests/f_crashdisk/name
new file mode 100644
index 0000000..2b28207
--- /dev/null
+++ b/tests/f_crashdisk/name
@@ -0,0 +1 @@
+superblock with illegal values
diff --git a/tests/f_crashdisk/script b/tests/f_crashdisk/script
new file mode 100644
index 0000000..8ab2b9c
--- /dev/null
+++ b/tests/f_crashdisk/script
@@ -0,0 +1,2 @@
+ONE_PASS_ONLY="true"
+. $cmd_dir/run_e2fsck