From owner-freebsd-questions Fri Feb 12 15:44:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23770 for freebsd-questions-outgoing; Fri, 12 Feb 1999 15:44:59 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from schizo.cdsnet.net (schizo.cdsnet.net [204.118.244.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA23761 for ; Fri, 12 Feb 1999 15:44:57 -0800 (PST) (envelope-from mrcpu@internetcds.com) Received: from localhost (mrcpu@localhost) by schizo.cdsnet.net (8.8.8/8.7.3) with SMTP id PAA27771 for ; Fri, 12 Feb 1999 15:39:37 -0800 (PST) Date: Fri, 12 Feb 1999 15:39:37 -0800 (PST) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: questions@FreeBSD.ORG Subject: Fundamental vinum question I'm missing. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm using a very recent (last couple of days) 3.1-beta box, testing out vinum. It's working fine, except the vinum read config option doesn't seem to work. Here was my config file: drive drive1 device /dev/da2c drive drive2 device /dev/da3c drive drive3 device /dev/da4c volume vol0 plex org striped 32b sd length 4000m drive drive1 sd length 4000m drive drive2 sd length 4000m drive drive3 I can mount, it, and it works fine. I put /dev/da2 /dev/da3 /dev/da4 in rc.conf, in the vinum_disks section, but it never finds it in bootup, I have to manually read in the config each time, and then mount it. vinum read /dev/da2 /dev/da3 /dev/da4 Feb 12 15:43:14 manipulation /kernel: vinum: no drives found Feb 12 15:43:14 manipulation /kernel: vinum: no drives found However: manipulation# vinum create /etc/vinum.slices Feb 12 15:43:59 manipulation /kernel: vinum: drive drive1 is up Feb 12 15:43:59 manipulation /kernel: vinum: drive drive1 is up Feb 12 15:43:59 manipulation /kernel: vinum: drive drive2 is up Feb 12 15:43:59 manipulation /kernel: vinum: drive drive2 is up Feb 12 15:43:59 manipulation /kernel: vinum: drive drive3 is up Feb 12 15:43:59 manipulation /kernel: vinum: drive drive3 is up Feb 12 15:43:59 manipulation /kernel: vinum: vol0.p0 is up Feb 12 15:43:59 manipulation /kernel: vinum: vol0.p0 is up Feb 12 15:43:59 manipulation /kernel: vinum: vol0 is up Feb 12 15:43:59 manipulation /kernel: vinum: vol0 is up Feb 12 15:43:59 manipulation /kernel: vinum: vol0.p0 is up Feb 12 15:43:59 manipulation /kernel: vinum: vol0.p0 is up Configuration summary Drives: 3 (4 configured) Volumes: 1 (4 configured) Plexes: 1 (8 configured) Subdisks: 3 (16 configured) D drive1 State: up Device /dev/da2c D drive2 State: up Device /dev/da3c D drive3 State: up Device /dev/da4c V vol0 State: up Plexes: 1 Size: 11 GB P vol0.p0 S State: up Subdisks: 3 Size: 11 GB S vol0.p0.s0 State: up PO: 0 B Size: 4000 MB S vol0.p0.s1 State: up PO: 16 kB Size: 4000 MB S vol0.p0.s2 State: up PO: 32 kB Size: 4000 MB I must be mis-understanding how vinum read is supposed to work. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message