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

[Hans Reiser <reiser@namesys.com>]

Matthias Andree wrote:

>Gerrit Hannaert <degerrit@web.de> writes:
>
>  
>
>>Anyway, my first instinct told me to try Maxtor's 'Powermax' tool, and
>>lo and behold the 'Advanced Test' here found errors, and 'fixed' them,
>>whatever that means. (Can you believe these guys make you download a
>>3MB Windows executable in order to write a 1.44Mb floppy image which
>>is less than half full?? I had to bloody install Windows for
>>this... grr....)
>>    
>>
>
>So complain and ask them to make a gzipped floppy image for Linux and
>*BSD users, and offer to send them one :-)
>
>  
>
>>I think I will spend the next week working out a better backup
>>solution...
>>    
>>
>
>...and finding out if files have been damaged.
>
>  
>
>>Will Reiserfs4 have better bad block handling than this? When I see all the 
>>trouble involved in rescuing this filesystem, as much as I'm impressed with 
>>it I would think twice about using Reiserfs on any non-redundant (and 
>>certainly IDE) disks from now on. I hope I don't make any enemies by saying 
>>so.
>>    
>>
>
>Any file system can screw up if the hardware fails in the wrong
>place. If what I'd call "file header" blocks are struck, the file name
>(at least) is gone, on some file systems the whole file. So there.
>
>Are there file systems that checksum the files' and directory data, to
>be able to flag files as broken if a bad block strikes?
>
>  
>
Nikita wrote a badblocks patch.

The main reason for resisting doing it is that it is usually better to 
just write to the bad block, and let the hard drive remap the block.

Oleg, maybe send it into 2.5?

Hans