Re: run extensive check on root filesys?

["Andrew Smith" <rhml k1k2 com>]

To do a bad block check run:

nice badblocks -vs /dev/xxxx

'df' will give you the device (the first field in the output)

I run one of these every day on each of my 7 servers
(without "-s" coz it's a logged cron job)
The "-s" sometimes causes problems with the screen output
if it does find a badblock

You can run it without "nice" if you don't care about any other
processes running on the machine or your partition is only about
1 Gig or so in size or the CPU is very fast.

One problem ... badblocks doesn't know about the filesystem so
it doesn't know where the data actually starts and finishes, so
it usually runs off the end of the data and finds bad blocks in
the last few blocks on the partition that are not used by ext2
or ext3 (well it does for me on some of my servers :-)

-Cheers
-Andrew

> I managed to manipulate my root filesys unmounted when I booted the
> rescue  mode on the enigma install disk...
> 
> the /forcefsck file also works, but I believe it doesn't really do a 
> badblocks test and all...
> 
> Thanks for your help
> 
> Hans
> 
> On Wednesday 30 January 2002 13:12, you wrote:
>> On 2002-01-30, SainTiss wrote:
>> :I'd like to run an extensive check (fsck or e2fsck) on my root
>> filesystem, :but I can't do that when it's mounted... What's the best
>> way of achieving :this?
>>
>> Don't know about the "best" way, but you can do something like this to
>> force an fs check at boot-time (if you're too lazy to use a
>> rescue disk):
>>
>>  # su -l root
>>  # touch /forcefsck
>>  # reboot