Date: Tue, 12 Sep 2000 08:49:43 +0930 From: Greg Lehey <grog@lemis.com> To: Geoff Buckingham <geoffb@chuggalug.clues.com> Cc: scsi@FreeBSD.ORG Subject: Re: VInum creation problem Message-ID: <20000912084942.J19431@wantadilla.lemis.com> In-Reply-To: <20000911190423.A32285@chuggalug.clues.com>; from geoffb@chuggalug.clues.com on Mon, Sep 11, 2000 at 07:04:23PM %2B0100 References: <20000911190423.A32285@chuggalug.clues.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday, 11 September 2000 at 19:04:23 +0100, Geoff Buckingham wrote: > > I have been trying to set up a vinum volume both manually and with the > following config file. Within vinum I 'create /etc/vinum.conf' and the machine > panics. I would need to see a dump. > drive drive1 device /dev/da1e > <snip> > sd length 8683m drive drive16 > sd length 8683m drive drive4 > > trying to configure similar volumes from the vinum prompt produces errors as > follows: > > vinum -> mirror -v -n raid10 -s /dev/da7e /dev/da8e /dev/da9e /dev/da10e > drive vinumdrive0 device /dev/da7e > drive vinumdrive1 device /dev/da8e > drive vinumdrive2 device /dev/da9e > drive vinumdrive3 device /dev/da10e > Can't create drive vinumdrive3, device /dev/da10e: Invalid argument (22) Hmm. > The partitions that throw up errors remain consistant, though this does not > cause a panic as create does (this way uses 256k stripes which I do not believe > is the problem) No, it wouldn't be the stripe size. > There seems no obvious diference in disk label from those that work and those > that don't: > > f2trailerpark01# disklabel da10 > <snip> > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > c: 17783249 0 unused 0 0 # (Cyl. 0 - 1106*) > e: 17783249 0 vinum > > f2trailerpark01# disklabel da9 > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > c: 17783249 0 unused 0 0 # (Cyl. 0 - 1106*) > e: 17783249 0 vinum # (Cyl. 0 - 1106*) > > f2trailerpark01# uname -a > FreeBSD f2trailerpark01.films.redbus.co.uk 4.1-STABLE FreeBSD 4.1-STABLE #0: Mon Sep 11 15:39:59 BST 2000 root@f2trailerpark01.films.redbus.co.uk:/usr/obj/usr/src/sys/GENERIC i386 > > nore in dmesg output: > > da9 at ahc2 bus 0 target 4 lun 0 > da9: <QUANTUM ATLAS V 9 SCA 0201> Fixed Direct Access SCSI-3 device > da9: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled > da9: 8683MB (17783249 512 byte sectors: 255H 63S/T 1106C) > da10 at ahc2 bus 0 target 5 lun 0 > da10: <QUANTUM ATLAS V 9 SCA 0201> Fixed Direct Access SCSI-3 device > da10: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled > da10: 8683MB (17783249 512 byte sectors: 255H 63S/T 1106C) > > NB these drives are on two busses before anyone gets worried about numbers :-) Yes, that's clear from the dmesg. > The machine has a full set of da* devices. > > Any Ideas? The best I can think of here would be a parse error, but I've seen other people go up to 32 drives (after which there *is* a problem). I've had up to about 12 devices on my test box, but they weren't all SCSI. A couple of questions: 1. Does the command-line error always start with da10? 2. Can you get a dump? Take a look at http://www.vinumvm.org/how-to-debug.html and send me in the info I need, and I'll look at it right away. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000912084942.J19431>