vitalif
/
e2fsprogs
mirror of https://github.com/vitalif/e2fsprogs
1
0
Fork 0
Code Issues Releases Wiki Activity
e2fsprogs/tests/f_crashdisk/expect.1

12 lines
516 B
Groff
Raw Normal View History

e2fsck: report ext2fs_open2() and ext2fs_check_desc() errors Print the actual errors returned by ext2fs_open2() and ext2fs_check_desc() before we fall back to the backup block group descriptors so that it's easier to see if there is some obscure failure that is causing e2fsck to think that it should use the backup block group descriptors. Addresses-Google-Bug: #6208183 Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
2012-03-22 07:40:24 +04:00
ext2fs_open2: The ext2 superblock is corrupt
e2fsck: If the superblock is corrupt, automatically retry with the backup sb E2fsck currently only retries with the backup superblock if the primary superblock is missing (e.g., overwritten with garbage). If the superblock is just corrupted enough that it looks like ext2/3/4 superblock, but it is corrupt enough that ext2fs_open2() returns an error, e2fsck stops without retrying. Let's fix this oversight. Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
2007-09-08 00:54:11 +04:00
../e2fsck/e2fsck: Superblock invalid, trying backup blocks...
tests: use /tmp for scratch files The /tmp directory is often a memory based file system, and using this can speed up running the regression test suite. Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
2011-07-09 20:08:10 +04:00
../e2fsck/e2fsck: The ext2 superblock is corrupt while trying to open test.img
Many files: Checked in e2fsprogs 1.05
1997-04-29 18:53:37 +04:00
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
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>
Exit status is 8