Re: how to control how often smartd-runner fires.

On 19/01/17 09:51 AM, mathog wrote:
> It is dumb, dumb, dumb that one must scan an entire disk to do this 
> whenthe disk already knows exactly where those blocks are - it just 
> will notdivulge the information! The result is that it takes a very 
> long time
> and is very inconvenient to fix this issue when it should take about 100
> milliseconds and be straightforward.

Thanks for being honest about that, sometimes guys try to convince you 
that it's all for the best when really it is dumb -- let's just admit it 
to ourselves and try to cope.
>
>
> but I don't think that badblocks has that ability.  Nor does smartctl
> have a nondestructive read then write mode.  Somebody please correct me
> if I'm wrong on that point. On the other hand, if you see pending
> sectors on a RAID disk, you're probably going to want to replace it
> right away in any case.
But you'd think that some whipper-snapper ace would write something.  
Just from what I read at that link posted yesterday it sounded like it 
might even be scriptable.  And you'd also think that there'd be a 
utility that let you know which files were effected so that you could do 
something about it.  At that  point, you'd just have to read the file to 
clear the error, no?  Then make your backups and all is right with the 
world.

In my case, I think the disk got bashed when running so it trashed some 
part of the disk, but its otherwise fine, cuz it's been 77 pending 
sectors for literally years otherwise of course I'd just replace the thing.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot