Date: Sun, 30 Nov 2008 16:35:58 +0100 From: Ulf Lilleengen <lulf@stud.ntnu.no> To: Hilko Meyer <hilko.meyer@gmx.de> Cc: adnan@hochpass.uni-hannover.de, freebsd-geom@freebsd.org Subject: Re: System freeze with gvinum Message-ID: <20081130153558.GA2120@nobby.lan> In-Reply-To: <fmg3j4lkbngkmcm41lvbrjvuj2o4iagcvb@4ax.com> References: <fmg3j4lkbngkmcm41lvbrjvuj2o4iagcvb@4ax.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Nov 29, 2008 at 11:47:59PM +0100, Hilko Meyer wrote: > Hi, > > 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? This might be a gvinum bug, but can also be a problem with the sata driver. > > 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? -- Ulf Lilleengen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081130153558.GA2120>