From owner-freebsd-questions Mon Dec 27 15: 2:21 1999 Delivered-To: freebsd-questions@freebsd.org Received: from game.over.net (game.over.net [193.189.189.100]) by hub.freebsd.org (Postfix) with ESMTP id D578215318 for ; Mon, 27 Dec 1999 15:02:17 -0800 (PST) (envelope-from tomaz.borstnar@over.net) Received: from [212.30.94.90] ([212.30.94.90]:16167 "EHLO user") by mail.over.net with ESMTP id ; Tue, 28 Dec 1999 00:01:53 +0100 Message-Id: <4.2.2.19991227235355.05918f00@193.189.189.100> X-Yes: No X-Mailer: Easy To Guess Mailer 1999 Date: Mon, 27 Dec 1999 23:56:54 -0100 To: Greg Lehey From: Tomaz Borstnar Subject: Re: vinum in FreeBSD 3.4, concat-ed plexes and reviving state Cc: freebsd-questions@FreeBSD.ORG In-Reply-To: <19991227120959.T1316@freebie.lemis.com> References: <4.2.2.19991227014323.00cb75c0@193.189.189.100> <4.2.2.19991227014323.00cb75c0@193.189.189.100> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:39 AM 12/27/99 , Greg Lehey wrote the following message: >If you want them to come up immediately, ignoring the obvious fact >that the data on the subdisks is not consistent, use the 'setupstate' >keyword here: > > volume var setupstate Yes, this was it! I redid the configuration and everything came up just fine! >It would probably take an hour or two. The problem here is that you >need to start the revive manually, and the state doesn't change. The >l -V output will also show that the revive pointer is set to 0. Maybe >I need a better name than 'reviving'. 'needs reviving' might be >better, but it looks funny in messages like > > vinum: var.p0 is needs reviving. 'needs manual intervention. See under reviving in vinum (4).' Thanks for help! Works nice once you understand it. Reading and rereading manuals is essential in making vinum running for the first time. Tomaz ---- Tomaz Borstnar "Love is the answer to the final question you ask" - Unknown To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message