Re: mke2fs checking bad blocks
Thanks Sven. Will it be any problem if I quit it by pressing Ctr-c? If
I understand it correctly, the mke2fs -c is only check the bad block,
not write or format the disk, right?
By the way, it has not reached the maximum blocks yet, but it seems it
need to run another 3 days to finishe it. I cannot level my machine on
so long.
Thanks.
Jupiter
On Sun, Aug 9, 2009 at 8:10 PM, Sven Joachim<svenjoac@gmx.de> wrote:
> On 2009-08-09 11:51 +0200, 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
>> mke2fs 1.40-WIP (14-Nov-2006)
>
> This is an old version, and it may be that you hit bug #411838¹ or some
> other problem that has been fixed in the meantime. I would definitely
> try a newer version on such a big filesystem.
>
>> Filesystem label=
>> OS type: Linux
>> Block size=4096 (log=2)
>> Fragment size=4096 (log=2)
>> 122109952 inodes, 244190008 blocks
>
> This indicates that the right boundary of 244190007 is at least close.
>
> Sven
>
>
> ¹ http://bugs.debian.org/411838
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>
Reply to: