Re: Corruption: --fix-fixable results in all nlink values = 0

[Hans Reiser <reiser@namesys.com>]

Gerrit Hannaert wrote:

> Hans Reiser wrote:
>
>> It is not that I oppose putting it into the tree with a fixed key for 
>> the file holding it, it is that I want us to work on other things 
>> instead.
>>
>> Hans
>
>
>
> Why not just run 'badblocks' (or the failure mechanism which now 
> aborts with "bread: Cannot read a block") as an (optional) part of 
> fsck and use the output in a bad-block-marking phase? 

This is good UI design.  Vitaly....

> Then you don't need to store the list of bad blocks anywhere, at least 
> not for fsck anyway ;-). Personally though, as a user, I'd like to 
> confirm the list of bad blocks in this case (in case it's too large I 
> might decide not to do it...)
>
> It wasn't even clear to me until last week that the hard disk *also* 
> did remapping of bad blocks, whether automatically or with some 
> vendor-tool. Perhaps any fsck failure due to hardware error should 
> recommend using low-level disk-checking tools provided by hard disk 
> vendors prior to taking any action itself?
>
> - Gerrit
>
>
>
>