From: Bruce Allen <ballen@gr...> - 2004-05-27 13:57:38
> > Did you ever get a reply to your May 17th posting about bad block
> > reallocation? If not, redirect it to smartmontools-support@...
> > and I'll answer it.
> Well, I was told that writing to a bad block will make the drive itself
> remap the bad block internally:
> > From: Malcolm V <farkit@...>
> > Subject: Re: [SLUG] smartctl drive monitoring
> > Date: Tue, 18 May 2004 00:09:56 +1000
> > To: Sydney Linux Users Group <slug@...>
> > On Mon, 2004-05-17 at 23:41, lukekendall@... wrote:
> > <snipped>
> > > Anyway, my question is: how does writing something to a bad block
> > > force the disk to reallocate the block? And, is it the disc that does
> > > this, or Linux?
> > When the disk itself cannot write to the block, it does the
> > reallocation, if it is able (It only has a certain number of spare
> > blocks).
> > Why would you manually want to force the block reallocation? After all,
> > the next time a write is attempted to that block, the disk will
> > automatically re-allocate it.
The point is that you might not EVER attempt a write to that block. For
example, support the block is part of the file /etc/termcap (which you
This leaves you in the situation where a file is not readable.
> > My guess is file recovery. Of course using the stated method means you
> > will recover a file with a bunch of 0s where there once was data, but at
> > least you can recovery the data after the bad block...
Yes, sort of. But more to the point is file IDENTIFICATION. You'd like
to know WHAT file is damanged (unreadable) to take corrective action.
> Is that correct? I really have to get off my backside and follow the
> recipe in http://smartmontools.sourceforge.net/BadBlockHowTo.txt to
> clear the error!
Close enough. Follow the recipe to figure out what file contains the
Get latest updates about Open Source Projects, Conferences and News.