From owner-freebsd-current Sun Jan 17 22:59:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA28849 for freebsd-current-outgoing; Sun, 17 Jan 1999 22:59:03 -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 WAA28843 for ; Sun, 17 Jan 1999 22:58:58 -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 RAA26018; Mon, 18 Jan 1999 17:28:53 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.2/8.9.0) id RAA00500; Mon, 18 Jan 1999 17:28:51 +1030 (CST) Date: Mon, 18 Jan 1999 17:28:51 +1030 From: Greg Lehey To: Makoto MATSUSHITA Cc: current@FreeBSD.ORG Subject: Re: vinum is always started at boot-time... Message-ID: <19990118172851.A474@freebie.lemis.com> References: <19990118153804.D55525@freebie.lemis.com> <19990118153804.D55525@freebie.lemis.com> <19990118151934P.matusita@jp.FreeBSD.ORG> <19990118151509G.matusita@ics.es.osaka-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990118151509G.matusita@ics.es.osaka-u.ac.jp>; from Makoto MATSUSHITA on Mon, Jan 18, 1999 at 03:15:09PM +0900 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 Monday, 18 January 1999 at 15:15:09 +0900, Makoto MATSUSHITA wrote: > > matusita> It works fine, however, sorry I have only ONE volume so how > matusita> it goes if two or more volumes are defined (note that 'vinum > matusita> read' takes only one argument). > > And, this code causes *duplicate* vinum information, if we do shutdown > to single-user mode and then try to come back to the multi-user world > (this causes to rerun /etc/rc, rerun 'vinum read' command, and dup them). There is a bug in the current version of Vinum which would allow this, but it's been fixed in the new megacommit I'm preparing. For example: Jan 18 15:36:36 panic /kernel: vinum: reading configuration from /dev/sd4h Jan 18 15:36:37 panic /kernel: vinum: updating configuration from /dev/sd3h Jan 18 15:36:38 panic /kernel: vinum: updating configuration from /dev/sd2h Jan 18 15:36:39 panic /kernel: vinum: updating configuration from /dev/sd1h Jan 18 15:38:35 panic /kernel: vinum: already read config from drive1 Jan 18 15:38:35 panic /kernel: vinum: already read config from drive2 Jan 18 15:38:35 panic /kernel: vinum: already read config from drive3 Jan 18 15:38:35 panic /kernel: vinum: already read config from drive4 Don't worry about the panic; that's the name of the system :-) You'll also notice that the order of reading is not the order in which the names are specified; Vinum starts with the newest config and works back. > Somebody may say that's bad... If you've tripped over the bug, `bad' is an understatement. It can completely tear your config apart. 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