From owner-freebsd-stable Fri Mar 3 7:49:17 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 8F6CA37B625 for ; Fri, 3 Mar 2000 07:49:14 -0800 (PST) (envelope-from gritton@iserver.com) Received: by gatekeeper.veriohosting.com; Fri, 3 Mar 2000 08:49:07 -0700 (MST) Received: from unknown(192.168.1.110) by gatekeeper.veriohosting.com via smap (V3.1.1) id xma010028; Fri, 3 Mar 00 08:49:02 -0700 Received: by guppy.orem.iserver.com; Fri, 3 Mar 2000 08:48:34 -0700 (MST) To: stable@freebsd.org Cc: jeff-ml@mountin.net Subject: Re: recent vinum changes References: <3.0.3.32.20000303072732.00989b20@207.227.119.2> From: Jamie Gritton Date: 03 Mar 2000 08:48:34 -0700 In-Reply-To: "Jeffrey J. Mountin"'s message of "Fri, 03 Mar 2000 07:27:32 -0600" Message-ID: Lines: 26 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jeffrey J. Mountin" writes: >> Generally, a "vinum start" on the previously dead plex... > What was the previous state of the dead plex and it's subdisks? The plex is faulty and the subdisk is stale. > I've had subdisks go "stale" or even "faulty" by themsleves or by design > (ala testing), but the plex is only "down" (if that's what you mean by > "dead"). These are generally bona fide hardware errors, i.e. a disk that won't spin up. > From your first message the loss of data on the "up" plex when reviving > isn't reassuring, but I've blown up plexes various ways and recovered most > every time. Note the "most" covers the more exotic and crazy ideas. The chance of recovery seems to decrease with usage of the system. An idle but non-single-user system weill usually make it through the recover OK, but then panic on some variety of filesystem errors, and be repairable with "only" a few dozen lost+found files. Generally, things are so bad, fsck can't find a superblock on the "good" half of the mirror. - Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message