Hi, 

I have set upp Softraid with 5*36.5GB (Maxtor) using RAID-5.
(3 disks on onboard (Athlon) VIA controller, 2 disks on PDC20262)


The setup worked ok and I created a file system with the following
data:
Block size:               4096
Fragment size:            4096
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         1024
Inode blocks per group:   32

(128k / inode)

This results in a ~145GB filesystem. 



I use the following software:
2.2.13
md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12
ide patch from Andre Hedrick (~Nov 10)

The PROBLEM:

Running fsck on this filesystem _allways_ reports a _LOT OF_
errors. Automatic check at bootup never works, I allways have to do a
manuall check. 
Running fsck -y takes several hours (it restarts several times,
allways after reporting (and fixing) a lot of errors (100+). 

It seems to me as if I have problem with corrupted data. 

I would like to try this with the latest 2.2.14pre -kernel + softraid
+ latest ide-patch but the softraid patch does not apply to this.


Anyone who has an idea?

Regards
/Jakob


PS.

The errors I get from fsck is:


Inode 1049224 is in use, but has dtime set.  Fix<y>? yes

Inode 1049224 has imagic flag set.  Clear<y>? yes

<<<< repeated xxx times >>>>

Inode 1049389 has illegal block(s).  Clear<y>? yes

Illegal block #0 (1403708311) in inode 1049389.  CLEARED.
Illegal block #1 (1142830631) in inode 1049389.  CLEARED.
Illegal block #2 (62958259) in inode 1049389.  CLEARED.
Illegal block #3 (67192161) in inode 1049389.  CLEARED.
Illegal block #4 (716604184) in inode 1049389.  CLEARED.
Illegal block #6 (1862402048) in inode 1049389.  CLEARED.
Illegal block #7 (1288048149) in inode 1049389.  CLEARED.
Illegal block #8 (3056304705) in inode 1049389.  CLEARED.
Illegal block #9 (3648820807) in inode 1049389.  CLEARED.
Illegal block #10 (698222959) in inode 1049389.  CLEARED.
Illegal block #11 (1716902030) in inode 1049389.  CLEARED.
Too many illegal blocks in inode 1049389.
Clear inode<y>? yes

<<<< repeated xxx times >>>>
-- 

Reply via email to