From owner-freebsd-questions Tue Nov 2 9:27:10 1999 Delivered-To: freebsd-questions@freebsd.org Received: from cc942873-a.ewndsr1.nj.home.com (cc942873-a.ewndsr1.nj.home.com [24.2.89.207]) by hub.freebsd.org (Postfix) with ESMTP id 4095B14A09 for ; Tue, 2 Nov 1999 09:27:03 -0800 (PST) (envelope-from cjc@cc942873-a.ewndsr1.nj.home.com) Received: (from cjc@localhost) by cc942873-a.ewndsr1.nj.home.com (8.9.3/8.9.3) id MAA05506; Tue, 2 Nov 1999 12:30:16 -0500 (EST) (envelope-from cjc) From: "Crist J. Clark" Message-Id: <199911021730.MAA05506@cc942873-a.ewndsr1.nj.home.com> Subject: Re: Recovering vinum Volume In-Reply-To: <19991102085310.03762@mojave.sitaranetworks.com> from Greg Lehey at "Nov 2, 1999 08:53:10 am" To: grog@lemis.com (Greg Lehey) Date: Tue, 2 Nov 1999 12:30:16 -0500 (EST) Cc: cjclark@home.com, freebsd-questions@FreeBSD.ORG (FreeBSD Questions), Greg@cc942873-a.ewndsr1.nj.home.com, Lehey@cc942873-a.ewndsr1.nj.home.com Reply-To: cjclark@home.com X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote, > On Monday, 1 November 1999 at 20:52:39 -0500, Crist J. Clark wrote: [snip] > > but I'm not sure how to get at it. A 'stop' and 'start' does not > > seem to fix it, and anything stronger than that has foreboding > > warnings in the manpages and could cause me to lose the data. I'd > > like to be sure of what to try before I do this. > > You don't give the exact commands. What does 'vinum start > scsivol.p0.s1' say? If that doesn't work, I have deep magic which > will, but I don't want to use it indiscriminately. Well, just doing, # vinum start scsivol.p0.s1 scsivol.p0.s1 is already up # vinum start scsivol.p0.s0 # vinum start scsivol.p0.s2 Seems to be not-so-deep magic that works. I had just been doing, # vinum stop # vinum start And making the assumption that 'vinum start' was pretty much identical to what you recommend that I do. That is, I figured a 'vinum start' went through and tried to start each subdisk individually. I was mistaken. Reviewing the vinum(8) manpage, specifically the details on the 'start' command, there are a number of bullets that discuss what happens to a subdisk when the start command is issued for it, and the subdisk is in a given state. There is no mention of what happens to a 'crashed' disk. That might have been helpful. I am not exactly sure how the documentation could have gotten the point that 'vinum start' is not identical to starting each object individually. Maybe it is just me. Thanks for the help. Prompt and to the point as usual. -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message