Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 30 Nov 2008 21:18:24 +0100
From:      Hilko Meyer <Hilko.Meyer@gmx.de>
To:        Ulf Lilleengen <lulf@stud.ntnu.no>
Cc:        adnan@hochpass.uni-hannover.de, freebsd-geom@freebsd.org
Subject:   Re: System freeze with gvinum
Message-ID:  <des5j4pqfbceh1hg4ad26arivjdmcqvr7m@mail.gmx.net>
In-Reply-To: <20081130153558.GA2120@nobby.lan>
References:  <fmg3j4lkbngkmcm41lvbrjvuj2o4iagcvb@4ax.com> <20081130153558.GA2120@nobby.lan>

next in thread | previous in thread | raw e-mail | index | archive | help
Ulf Lilleengen schrieb:
>On Sat, Nov 29, 2008 at 11:47:59PM +0100, Hilko Meyer wrote:
>>=20
>> I've tried to set up a raid-5 over three disks with gvinum today with =
this
>> gvinum.conf:
>>=20
>> drive sata1 device /dev/ad4
>> drive sata2 device /dev/ad5
>> drive sata3 device /dev/ad6
>>=20
>> 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
>>=20
>> 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=20
>> 6.4-RELEASE that was compiled today. What can I do to debug this =
problem?
>>=20
>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
>>=20
>> 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?des5j4pqfbceh1hg4ad26arivjdmcqvr7m>