Re: forwarded message from Jan De Luyck

[Hans Reiser <reiser@namesys.com>]

Vitaly Fertman wrote:

>On Wednesday 10 December 2003 22:54, Hans Reiser wrote:
>  
>
>>Vitaly Fertman wrote:
>>    
>>
>>>Hello,
>>>
>>>      
>>>
>>>>Hello,
>>>>
>>>>Today I discovered this in my syslogs, after something strange
>>>>happening to XFree86 (hung at startup, then dumped me back to the
>>>>console)
>>>>
>>>>is_leaf: free space seems wrong: level=1, nr_items=41, free_space=65224
>>>>rdkey vs-5150: search_by_key: invalid format found in block 283191. Fsck?
>>>>vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find
>>>>stat data of [11 12795 0x0 SD] is_leaf: free space seems wrong: level=1,
>>>>nr_items=41, free_space=65224 rdkey vs-5150: search_by_key: invalid
>>>>format found in block 283191. Fsck? vs-13070:
>>>>reiserfs_read_locked_inode: i/o failure occurred trying to find stat
>>>>data of [11 12798 0x0 SD]
>>>>        
>>>>
>>>this all about fs corruptions. fsck is needed.
>>>      
>>>
>>is this a failure due to bad sector on the drive?
>>    
>>
>
>No, we return EIO in many places if some data corruption is found 
>even if the hardware has worked ok. A stat data has not been found
>here and EIO is returned.
>
>--
>Thanks,
>Vitaly Fertman
>
>
>  
>
fix the code to have a more accurate description.  This is not what I 
would consider an IO error, and it should not describe itself to users 
that way.

Also, please attempt to determine if this is happening on a file system 
that has only had a recent kernel running on it.  I am concerned that we 
might have a bug in recent V3.

-- 
Hans