System freeze with gvinum

[Hilko Meyer]

Ulf Lilleengen schrieb:
>On Sat, Nov 29, 2008 at 11:47:59PM +0100, Hilko Meyer wrote:
>> 
>> I've tried to set up a raid-5 over three disks with gvinum today with this
>> gvinum.conf:
>> 
>> drive sata1 device /dev/ad4
>> drive sata2 device /dev/ad5
>> drive sata3 device /dev/ad6
>> 
>> volume homes_raid5
>>   plex org raid5 512k
>>     sd length 238465m drive sata1
>>     sd length 238465m drive sata2
>>     sd length 238465m drive sata3
>> volume dump_raid5
>>   plex org raid5 512k
>>     sd length 238465m drive sata1
>>     sd length 238465m drive sata2
>>     sd length 238465m drive sata3
>> 
>> Every time I tried to run newfs on one of the volumes it stucked and the
>> complete system freezed, so I cannot provide a coredump. The system runs 
>> 6.4-RELEASE that was compiled today. What can I do to debug this problem?
>> 
>Hmm, do you have any console output before the freeze? Such as g_* messages?

Unfortunately nothing.

>This might be a gvinum bug, but can also be a problem with the sata driver.

How can I test the sata driver?  After writing the mail yesterday we
used dump|restore to copy several gigabytes to ad4s1a and no problems
occured in this test.

>> Involved hardware:
>> atapci0: <nVidia nForce MCP65 UDMA133 controller>
>> ad4: 476940MB <Seagate ST3500320NS SN05> at ata2-master UDMA33
>> ad5: 476940MB <Seagate ST3500320NS SN05> at ata2-slave UDMA33
>> ad6: 476940MB <Seagate ST3500320NS SN05> at ata3-master UDMA33
>> 
>> BTW: That are SATA-disks. Why they are reported as UDMA33?
>Seems weird. Maybe there are some bios settings turning of AHCI-mode?

Ah, I think I know were to look for that. I'll try tomorrow.

bye,
Hilko