From owner-freebsd-questions  Tue Jan 23  8:56:17 2001
Delivered-To: freebsd-questions@freebsd.org
Received: from neo.it.comsat.com (neo.it.comsat.com [134.133.253.26])
	by hub.freebsd.org (Postfix) with ESMTP id 0E49C37B400
	for <freebsd-questions@freebsd.org>; Tue, 23 Jan 2001 08:55:55 -0800 (PST)
Received: from omnivor1.rsp.comsat.com (omnivor1 [134.133.178.45])
	by neo.it.comsat.com (Switch-2.0.1/Switch-2.0.1) with ESMTP id f0NGmVJ19904
	for <freebsd-questions@freebsd.org>; Tue, 23 Jan 2001 11:48:31 -0500 (EST)
Received: from omnivor1.rsp.comsat.com ([134.133.178.45]) by omnivor1.rsp.comsat.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id D3RF2GMQ; Tue, 23 Jan 2001 11:53:32 -0500
Received: FROM cqgate6.cmc.comsat.com BY omnivor1.rsp.comsat.com ; Tue Jan 23 11:53:31 2001 -0500
Received: from ccMail by cqgate6.cmc.comsat.com
  (IMA Internet Exchange 3.13) id 001FEBD0; Tue, 23 Jan 2001 12:05:26 -0500
Mime-Version: 1.0
Date: Tue, 23 Jan 2001 11:54:09 -0500
Message-ID: <001FEBD0.C22219@comsat.com>
From: Marc.Giannoni@comsat.com
Subject: vinum start problem in /etc/rc
To: freebsd-questions@freebsd.org
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Content-Description: cc:Mail note part
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

     Hi:
     
     I believe there may be a problem with the vinum startup commands in 
     /etc/rc.   Whenever I drop (my host) down to Single User mode, the 
     vinum daemon is not stopped - which appears to be OK although FreeBSD 
     does issue a warning.   When returning (my host) to Multi User mode, 
     /etc/rc performs another "vinum start", AND THE VINUM DAEMON IS STILL 
     RUNNING!   Vinum does not seem to like this (being started twice) and 
     appears to causes the vinum disks to assume a "down" state.   I 
     mistakenly tried to start these disks individually and subsequently 
     corrupted a few subdisks which caused me to trash my file system.   
     (I've gotta be more careful with these vinum commands in the future!!)
     
     I've not seen any comments about this issue, only the usual 
     start_vinum="YES" line in /etc/rc.conf.   Should "/etc/rc" perform a 
     process table check to ensure that the vinum daemon is NOT active 
     prior to performing the "vinum start" command?  Is there a special 
     "vinum" option that protect against recursive "vinum start(s)"?   
     Should all vinum file systems be unmounted when dropping to Single 
     User mode so that the vinum daemon can be (will be) stopped?  
     
     Thanks
     
     Marc


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message