Debian Bug report logs - #768113
mke2fs -c -c should also report total percentage

Reply or subscribe to this bug.

Display info messages

Message #5 received at [email protected] (full text, mbox, reply):

From: 積丹尼 Dan Jacobson <[email protected]>

To: Debian Bug Tracking System <[email protected]>

Subject: mke2fs -c -c should also report total percentage

Date: Wed, 05 Nov 2014 10:41:54 +0800

Package: e2fsprogs
Version: 1.42.12-1
Severity: wishlist
File: /sbin/mke2fs

mke2fs -c -c should also report total percentage.
Apparently it makes three passes, each time reporting just that pass'
percentage of completion. But then it just starts on the next pass.
The user is left with no idea of when it will end.
So it should do a better job of giving a user an idea of when it will
end.

Here we also see some other things, which I can't explain. Maybe
hardware problems?:

Weird, mke2fs succeeds but then fsck fails,

# mke2fs -t ext4 -c /dev/sdd2
mke2fs 1.42.12 (29-Aug-2014)
Creating filesystem with 512000 1k blocks and 128016 inodes
Filesystem UUID: 0e201fb0-72c5-457f-aef0-36641dbaac6f
Superblock backups stored on blocks:
        8193, 24577, 40961, 57345, 73729, 204801, 221185, 401409

Checking for bad blocks (read-only test): done
Allocating group tables: done
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done

# fsck.ext4 /dev/sdd2
e2fsck 1.42.12 (29-Aug-2014)
ext2fs_open2: Bad magic number in super-block
fsck.ext4: Superblock invalid, trying backup blocks...
fsck.ext4: Bad magic number in super-block while trying to open /dev/sdd2

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>

(dmesg doesn't show anything special.)
(Also the tips to do dmesg|tail should also perhaps mention journalctl|tail)

# mke2fs -t ext4 -c -c /dev/sdd2
mke2fs 1.42.12 (29-Aug-2014)
Creating filesystem with 512000 1k blocks and 128016 inodes
Filesystem UUID: bd2c590f-bf83-4167-853d-ee1220055416
Superblock backups stored on blocks:
        8193, 24577, 40961, 57345, 73729, 204801, 221185, 401409

Testing with pattern 0xaa: done
Reading and comparing: done
Testing with pattern 0x55: done
Reading and comparing: done
Testing with pattern 0xff: done
Reading and comparing: done
Testing with pattern 0x00: done
Reading and comparing: done
Allocating group tables: mke2fs: Could not allocate block in ext2 filesystem while trying to allocate filesystem tables

#

Wonder if that was bad.

Problem #2: -c -c prints several % done making the user think we're
almost done, only to begin on a different pattern.

Also the above 0/0/xxxx error report lines disappeared with the final
carriage return, so I can't copy them here.

Odd, after this everything works fine.

Send a report that this bug log contains spam.