spekulatius n00b


Joined: 20 May 2003 Posts: 28 Location: .de
|
Posted: Mon Jun 23, 2003 11:33 pm Post subject: serious problems with raid5 / promise controllers |
|
|
hello all,
in the last two weeks i had some time to convert my debian file server to gentoo. i did this right after i compiled my desktop system, which has also been a debian one. what i want to say with this: i am not new to linux, but new to gentoo, so give heavy in depth answers
but one thing i am really new to. problems with my raid 5. all i did was putting the raid 5 software array out of my server, reinstalled the whole system and compiled the xfs-sources for my kernel. i have a persistent superblock array, therefore i do not need a raidtab at the moment. the array was properly recognized, the devices of the disks have changed a bit, because i renewed the mainboard beforehand.
ok. now my problem. the array rebuilds far to often. it is ok that it does so if someone changes the devices and the beast wants to check itself. but it does this every reboot. it takes around 35 minutes, thats ok for its size but i think this is not necessary.
therefore i studied dmesg and found out the following:
Code: |
md: raid5 personality registered as nr 4
raid5: measuring checksumming speed
8regs : 1620.000 MB/sec
32regs : 1330.000 MB/sec
pII_mmx : 2809.600 MB/sec
p5_mmx : 3604.800 MB/sec
raid5: using function: p5_mmx (3604.800 MB/sec)
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
[events: 000000a0]
[events: 000000a0]
[events: 000000a0]
md: autorun ...
md: considering ide/host4/bus0/target0/lun0/part1 ...
md: adding ide/host4/bus0/target0/lun0/part1 ...
md: adding ide/host2/bus1/target0/lun0/part1 ...
md: adding ide/host2/bus0/target0/lun0/part1 ...
md: created md0
md: bind<ide/host2/bus0/target0/lun0/part1,1>
md: bind<ide/host2/bus1/target0/lun0/part1,2>
md: bind<ide/host4/bus0/target0/lun0/part1,3>
md: running: <ide/host4/bus0/target0/lun0/part1><ide/host2/bus1/target0/lun0/part1><ide/host2/bus0/target0/lun0/part1>
md: ide/host4/bus0/target0/lun0/part1's event counter: 000000a0
md: ide/host2/bus1/target0/lun0/part1's event counter: 000000a0
md: ide/host2/bus0/target0/lun0/part1's event counter: 000000a0
md: md0: raid array is not clean -- starting background reconstruction
md0: max total readahead window set to 496k
md0: 2 data-disks, max readahead per data-disk: 248k
raid5: device ide/host4/bus0/target0/lun0/part1 operational as raid disk 2
raid5: device ide/host2/bus1/target0/lun0/part1 operational as raid disk 1
raid5: device ide/host2/bus0/target0/lun0/part1 operational as raid disk 0
raid5: allocated 3291kB for md0
raid5: raid level 5 set md0 active with 3 out of 3 devices, algorithm 0
raid5: raid set md0 not clean; reconstructing parity
RAID5 conf printout:
--- rd:3 wd:3 fd:0
disk 0, s:0, o:1, n:0 rd:0 us:1 dev:ide/host2/bus0/target0/lun0/part1
disk 1, s:0, o:1, n:1 rd:1 us:1 dev:ide/host2/bus1/target0/lun0/part1
disk 2, s:0, o:1, n:2 rd:2 us:1 dev:ide/host4/bus0/target0/lun0/part1
RAID5 conf printout:
--- rd:3 wd:3 fd:0
disk 0, s:0, o:1, n:0 rd:0 us:1 dev:ide/host2/bus0/target0/lun0/part1
disk 1, s:0, o:1, n:1 rd:1 us:1 dev:ide/host2/bus1/target0/lun0/part1
disk 2, s:0, o:1, n:2 rd:2 us:1 dev:ide/host4/bus0/target0/lun0/part1
md: updating md0 RAID superblock on device
md: ide/host4/bus0/target0/lun0/part1 [events: 000000a1]<6>(write) ide/host4/bus0/target0/lun0/part1's sb offset: 80043712
md: syncing RAID array md0
md: minimum _guaranteed_ reconstruction speed: 100 KB/sec/disc.
md: using maximum available idle IO bandwith (but not more than 100000 KB/sec) for reconstruction.
md: using 124k window, over a total of 80043136 blocks.
md: ide/host2/bus1/target0/lun0/part1 [events: 000000a1]<6>(write) ide/host2/bus1/target0/lun0/part1's sb offset: 80043136
|
Code: |
spurious 8259A interrupt: IRQ7.
spurious 8259A interrupt: IRQ15.
|
Code: |
md: ide/host2/bus0/target0/lun0/part1 [events: 000000a1]<6>(write) ide/host2/bus0/target0/lun0/part1's sb offset: 80043136
md: ... autorun DONE.
|
as you might recognize: in the second code box of the dmesg snippet, spurious interrupts appear. irq7 is the first, irq 15 the second controller i am using. to be exact: promise ultra 100tx2 and ultra 133tx2.
are there problems with these controllers?
why do they stop working and force my bus to reset?
list of facts:
- xfs-sources 2.4.20 with nforce2 agp patch
- a7n8x (non-deluxe)
- acpi disabled in kernel
- apm not (left it out already, didnt change anything)
now what? go for the highpoint controllers? (ok, i should go for 3ware.. but i am a student. sorry. no discussion. i like software raid )
thanks alot for your help,
greetings.
..::spekulatius::.. |
|