> While experimenting with badblocks -w on an unused partition I noticed
> that using ctrl-C to stop execution left a large number (e.g. 16,000) of
> locked buffers. The buffers didn't unlock after waiting some seconds, so
> I had to reboot the machine. Is this a known problem with badblocks?
>
> Regards,
> Bill
>
On my machine it's impossible to 'ctrl-c' running badblocks -w. :)
System is locked, I mean, everything stops until it finishes.
Pressing sysrq-m while it's running says there are no free pages.
After badblocks finishes, system is ready again.
It happens in all kernels from 2.0.29-32, 2.1.4x-70, no matter using
IDE or SCSI disks.
I kinda get used to that behaviour. :)
Regards,
-- Posted by Zlatko Calusic E-mail: <Zlatko.Calusic@CARNet.hr> --------------------------------------------------------------------- Modem sex begins with a handshake.