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

[Oleg Drokin <green@namesys.com>]

Hello!

On Mon, Aug 19, 2002 at 03:14:12PM +0400, Hans Reiser wrote:
> >>>>that you are using it everytime you find it though, that way if a 
> >>>>different sysadmin is running fsck, they can know why not all the blocks 
> >>>>they expect to be there are accessible.
> >>>Having some config files for this purpose is not good.
> >>>What if I have booted from rescue disk?
> >>That is why it is only the DEFAULT location, and (slight improvement 
> >>here) the user is prompted about whether to use it.
> >This is still too error prone, I think it is better to have this info on 
> >FS.
> How does that make it less error prone?  It sounds like more complex 
> code to me, especially considering that in the worst case the user 
> reruns badblocks to generate the data again.

Less error prone in the sence that the data is contained within FS itself, so
the only way to get it wrong is FS corruption due to HW problems/kernel bug.

If we only rely on expernal source, user might forget to specify this file
(or simply he can be unaware that there is such a file) and all bad blocks
would be marked as free to use, wrong list of bad blocks might be specified
and so on.

Bye,
    Oleg