From owner-freebsd-current Fri Jan 22 14:01:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20412 for freebsd-current-outgoing; Fri, 22 Jan 1999 14:01:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20273 for ; Fri, 22 Jan 1999 14:00:55 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id IAA27742; Sat, 23 Jan 1999 08:17:54 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.2/8.9.0) id IAA19627; Sat, 23 Jan 1999 08:17:08 +1030 (CST) Date: Sat, 23 Jan 1999 08:17:08 +1030 From: Greg Lehey To: Jake Cc: current@FreeBSD.ORG Subject: vinum read no longer works Message-ID: <19990123081708.I5697@freebie.lemis.com> References: <199901221723.JAA01151@h24-64-221-247.gv.wave.shaw.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199901221723.JAA01151@h24-64-221-247.gv.wave.shaw.ca>; from Jake on Fri, Jan 22, 1999 at 09:23:48AM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 22 January 1999 at 9:23:48 -0800, Jake wrote: > I can no longer bring up my vinum volume with the vinum read > command: > > vinum read /dev/wd0s1e /dev/wd2s1f > vinum read /dev/wd0s1e > vinum read /dev/wd2s1f > > all come back with > vinum: no drives Correct. As I explained in detail in my HEADS UP message a couple of days ago, you must now specify drives, not partitions. The correct command might be vinum read /dev/wd0 /dev/wd2 To quote the message: >> One way you can shoot yourself in the foot: the `read' command has >> changed. In the previous version, you specified the name of exactly >> one device containing a vinum partition. This is suboptimal, because >> it doesn't allow you to read multiple configurations, and it doesn't >> allow you to move drives around. In the new version, you *must* >> specify the names of *all* disks containing Vinum partitions. For >> example, if you have Vinum partitions /dev/da1h /dev/da2h /dev/da3h >> /dev/da4h /dev/da5h and /dev/da6h, you might previously have written: >> >> vinum read /dev/da3h >> >> Now you *must* write: >> >> vinum read /dev/da1 /dev/da2 /dev/da3 /dev/da4 /dev/da5 /dev/da6 >> >> If you do this wrong, you have the potential to wipe out your on-disk >> configuration. You can avoid this by disabling saving the >> configuration. Do this with the `setdaemon' command: >> >> # vinum >> vinum -> setdaemon 4 >> vinum -> read /dev/da1 /dev/da2 /dev/da3 /dev/da4 /dev/da5 /dev/da6 > I understand that all slices belonging to a volume must now be > passed to read, but that doesn't make any difference. Yes it does. As a result of the incorrect read command, you have probably obliterated your configuration. > I've modified /etc/rc to do a vinum create /etc/vinum.conf instead > and that works, but I thought read was the correct commmand. `read' is the correct command. The arguments you supplied are wrong. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message