Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 29 Nov 2008 23:47:59 +0100
From:      Hilko Meyer <hilko.meyer@gmx.de>
To:        freebsd-geom@freebsd.org
Cc:        adnan@hochpass.uni-hannover.de
Subject:   System freeze with gvinum
Message-ID:  <fmg3j4lkbngkmcm41lvbrjvuj2o4iagcvb@4ax.com>

next in thread | raw e-mail | index | archive | help
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?


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?

Thanks for your help in advance.

bye,
Hilko



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