Date: Thu, 21 Aug 2003 10:16:20 +0900 From: "lukek" <lukek@meibin.net> To: "FreeBSD" <freebsd-questions@freebsd.org> Subject: Re: Vinum Configuration File Message-ID: <000b01c36781$d855f560$080aa8c0@yujo> References: <000901c3677c$04b4cfb0$080aa8c0@yujo>
next in thread | previous in thread | raw e-mail | index | archive | help
Things got only marginally better, I now have errors about disks being full can someone tell me where that is comming from the disks are for all intents and purposes empty. 6: sd length 76g drive d1 ** 6 No space for on d1: No space left on device 7: sd length 76g drive d2 ** 7 Unnamed sd is not associated with a plex: Invalid argument 8: sd length 76g drive d3 ** 8 Unnamed sd is not associated with a plex: Invalid argument 3 drives: D d1 State: up Device /dev/ad1s1e Avail: 154140/76316 MB (201%) D d2 State: up Device /dev/ad2s1e Avail: 76316/76316 MB (100%) D d3 State: up Device /dev/ad3s1e Avail: 76316/76316 MB (100%) 1 volumes: V export State: up Plexes: 1 Size: 0 B 1 plexes: P export.p0 S State: up Subdisks: 0 Size: 0 B -1 subdisks: ----- Original Message ----- From: "lukek" <lukek@meibin.net> To: "FreeBSD" <freebsd-questions@freebsd.org> Sent: 2003年8月21日 9:34 Subject: Vinum Configuration File > Hello, > I am having a bit of trouble getting the conf file correct. I have listed > the devices and slice names but get the following error > > vinum -> create -f vinum.conf > 1: drive d1 /dev/ad1s1e > ** 1 Drive d1, invalid keyword: /dev/ad1s1e: Invalid argument > 2: drive d2 /dev/ad2s1e > ** 2 Drive d2, invalid keyword: /dev/ad2s1e: Invalid argument > 3: drive d3 /dev/ad3s1e > ** 3 Drive d3, invalid keyword: /dev/ad3s1e: Invalid argument > 0 drives: > 1 volumes: > V export State: down Plexes: 1 Size: 149 GB > > 1 plexes: > P export.p0 R5 State: faulty Subdisks: 3 Size: 149 GB > > 3 subdisks: > S export.p0.s0 State: crashed PO: 0 B Size: 74 GB > S export.p0.s1 State: crashed PO: 32 kB Size: 74 GB > S export.p0.s2 State: crashed PO: 64 kB Size: 74 GB > > The offending conf file looks like this > > drive d2 /dev/ad2s1e > drive d3 /dev/ad3s1e > volume export > plex org raid5 32k > sd length 76319MB drive d1 > sd length 76319MB drive d2 > sd length 76319MB drive d3 > > disklabel for the disks in question look like this > > tamachi# disklabel -r ad1 > # /dev/ad1c: > type: ESDI > disk: ad1s1 > <snip> > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > c: 156296322 0 unused 0 0 # (Cyl. 0 - > 9728*) > e: 156296322 0 4.2BSD 2048 16384 89 # (Cyl. 0 - > 9728*)a > > tamachi# disklabel -r ad2 > # /dev/ad2c: > type: ESDI > disk: ad2s1 > <snip> > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > c: 156296322 0 unused 0 0 # (Cyl. 0 - > 9728*) > e: 156296322 0 4.2BSD 2048 16384 89 # (Cyl. 0 - > 9728*) > > tamachi# disklabel -r ad3 > # /dev/ad3c: > type: ESDI > disk: ad3s1 > <snip> > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > c: 156296322 0 unused 0 0 # (Cyl. 0 - > 9728*) > e: 156296322 0 4.2BSD 2048 16384 89 # (Cyl. 0 - > 9728*) > > Can someone throw me a life ring here ? The fileserver has been down for a > day now due to hardware failures on the raid device and I am trying to use > Vinum to create a raid device with out much luck. > > Also, If I decided to do away with a certain configuration I have been using > resetconfig , will this allow me to start from scratch again ? > > Appreciate any assistance someone can offer on this. > > Thanks > > LukeK > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000b01c36781$d855f560$080aa8c0>