[prev in list] [next in list] [prev in thread] [next in thread] 

List:       reiserfs-devel
Subject:    Re: ReiserFS 3.6 errors
From:       Dan Oglesby <doglesby () teleformix ! com>
Date:       2005-03-29 20:48:35
Message-ID: 4249BF23.5090102 () teleformix ! com
[Download RAW message or body]

Alex Zarochentsev wrote:

>Hi,
>
>On Tue, Mar 29, 2005 at 09:58:33AM -0600, Dan Oglesby wrote:
>  
>
>>Greetings,
>>
>>I just finished installing a machine that uses ReiserFS v3.6 
>>filesystems, one of which is on a RAID-5 device off of a 3Ware 7506 
>>controller.
>>
>>After the build, a stress test was run that generates a lot of disk I/O, 
>>and I saw the following in dmesg:
>>
>>vs-500: unknown uniqueness 1162690892
>>vs-500: unknown uniqueness 1162690892
>>vs-500: unknown uniqueness 1162690892
>>vs-500: unknown uniqueness 1162690892
>>vs-500: unknown uniqueness 1162690892
>>vs-500: unknown uniqueness 1162690892
>>, item_len 14136, item_location 10272, free_space(entry_count) 11827
>>vs-5150: search_by_key: invalid format found in block 2029494. Fsck?
>>vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat 
>>data of [40 171378 0x0 SD]
>>is_leaf: item location seems wrong (second one): *3.6* [40 357194 0x0 
>>SD], item_len 44, item_location 2412, free_space(entry_count) 65535
>>vs-5150: search_by_key: invalid format found in block 3864557. Fsck?
>>vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat 
>>data of [40 357181 0x0 SD]
>>vs-500: unknown uniqueness 1647255672
>>vs-500: unknown uniqueness 1647255672
>>vs-500: unknown uniqueness 1647255672
>>vs-500: unknown uniqueness 1647255672
>>vs-500: unknown uniqueness 1647255672
>>vs-500: unknown uniqueness 1647255672
>>, item_len 27951, item_location 29803, free_space(entry_count) 28265
>>vs-5150: search_by_key: invalid format found in block 4488286. Fsck?
>>vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat 
>>data of [40 453681 0x0 SD]
>>
>>I did see something in the FAQ about requiring a reboot after changing 
>>partitions on a disk.  Unfortunately, I didn't see this until after the 
>>machine was built.  Could these errors be caused from a lack of a reboot 
>>between partitioning the disk and running mkreiserfs?
>>
>>This is on a RedHat 7.3 system, using kernel 2.4.20.
>>    
>>
>
>isn't it a vanilla 2.4.20 kernel from ftp.kernel.org?
>
>there were reports that reiserfs does not work well in RH kernels.  stock
>2.4.20 might work much better.  usually their kernels are patched a lot, some
>kernel patch may cause reiserfs instability.
>
>  
>
It's a 2.4.20 kernel from RedHat.  We're stuck using it because of 
dependancies of other software on the system, so we can't upgrade at the 
moment.

--Dan
[prev in list] [next in list] [prev in thread] [next in thread]