From owner-freebsd-stable Thu Mar 2 12:19:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gatekeeper.veriohosting.com (gatekeeper.veriohosting.com [192.41.0.2]) by hub.freebsd.org (Postfix) with ESMTP id F2F9137B51A for ; Thu, 2 Mar 2000 12:19:52 -0800 (PST) (envelope-from gritton@iserver.com) Received: by gatekeeper.veriohosting.com; Thu, 2 Mar 2000 13:19:52 -0700 (MST) Received: from unknown(192.168.1.110) by gatekeeper.veriohosting.com via smap (V3.1.1) id xma017909; Thu, 2 Mar 00 13:19:47 -0700 Received: by guppy.orem.iserver.com; Thu, 2 Mar 2000 13:19:27 -0700 (MST) To: Khetan Gajjar Cc: stable@freebsd.org Subject: Re: recent vinum changes References: From: Jamie Gritton Date: 02 Mar 2000 13:19:27 -0700 In-Reply-To: Khetan Gajjar's message of "Thu, 2 Mar 2000 22:03:00 +0200 (SAST)" Message-ID: Lines: 18 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Khetan Gajjar writes: > How are you reviving a vinum mirror ? I haven't yet had the > need to do so, but I'm dreading doing it now that you mention > this. Generally, a "vinum start" on the previously dead plex. It will usually revive OK if you do this in single-user, but any reasonable level of filesystem activity panics the system, and when it comes up, there's nothing left of /usr (on either half of the mirror). > What happens if one of the disks dies ? Does the machine > panic ? No, it does OK as long as you never try to revive. That's our current situation. - Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message