Re: mkreiserfs and big RAID-Systems

[Vitaly Fertman <vitaly@namesys.com>]

> Hi Vitaly,
>
> Am Mon, 2002-07-15 um 18.08 schrieb Vitaly Fertman:
> > > Here is the result
> > > [root@saturn6 mkreiserfs]# ./mkreiserfs /dev/sdf1
> > > Count of blocks on the device: 210096054
> >
> > As you can see block number is correct - 840384216 blocks.
> >
> > > bread: Cannot read a block # 210096053.
>
> it looks like every block on these devices that is aboth about
> Block-Number 18000000 is declared as a bad block in reiserfs, in ext2fs
> that doesnt happen. (Thats why i hve tried 'mkreiserfs /dev/sdf1
> 190000000) and i got ' bread: Cannot read a block # 189999999.'

Badblocks list is still disabled in reiserfs. And mkreiserfs just want
to read that block and the kernel (not reiserfs part of it) prints I/O 
error into syslog.

> > This is likely to be a bad block. Run
> >     /sbin/badblock -b 4096 /dev/sdf1 210096053 210096053
> > or with some range.
>
> i tried the command, but if i am right, i have to declare 120 G-Blocks
> as bad, and i dont believe that in every of my 5 RAID-Systems there is
> exactly 1 defect Harddisk.

badblock tests disk blocks, not reiserfs. And as you can see you cannot 
access some blocks on your device. This is not reiserfs problem. Test with
badblock that harddisk separately, test your RAID configuration, etc.

-- 

Thanks,
Vitaly Fertman