Re: mke2fs checking bad blocks

[Ron Johnson <ron.l.johnson@cox.net>]

On 2009-08-09 04:51, hce wrote:
> Hi,
>
> I have beening running following command to check an external USB 1 TB
> disk for more than 15 hours. I am not clear if the right corner of
> 244190007 is the maxinum blocks it should check or not. If it is, it
> seems that it has already exceeded the total blocks, but it is still
> running. What should I do, just quit it?
>
> ~$ /sbin/mke2fs -c /dev/sda1

sda???  Is your boot disk hda?

Is it plugged into a USB 1.1 port?

Also, I wouldn't be surprised if "check bad blocks" weren't 
inordinately slow even on internal disks.

> mke2fs 1.40-WIP (14-Nov-2006)
> Filesystem label=
> OS type: Linux
> Block size=4096 (log=2)
> Fragment size=4096 (log=2)
> 122109952 inodes, 244190008 blocks
> 12209500 blocks (5.00%) reserved for the super user
> First data block=0
> Maximum filesystem blocks=0
> 7453 block groups
> 32768 blocks per group, 32768 fragments per group
> 16384 inodes per group
> Superblock backups stored on blocks:
>         32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
>         4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
>         102400000, 214990848
>
> Checking for bad blocks (read-only test):        25582272/      244190007
>
> Thank you.
>
> Kind Regards,
>
> Jupiter


--
Scooty Puff, Sr
The Doom-Bringer