Date: Fri, 03 Mar 2000 07:27:32 -0600 From: "Jeffrey J. Mountin" <jeff-ml@mountin.net> To: Jamie Gritton <gritton@iserver.com>, Khetan Gajjar <khetan@uunet.co.za> Cc: stable@FreeBSD.ORG Subject: Re: recent vinum changes Message-ID: <3.0.3.32.20000303072732.00989b20@207.227.119.2> In-Reply-To: <x7itz55dm8.fsf@guppy.orem.iserver.com> References: <Khetan Gajjar's message of "Thu, 2 Mar 2000 22:03:00 %2B0200 (SAST)"> <Pine.BSF.4.21.0003022201340.39426-100000@bofh.ops.uunet.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
At 01:19 PM 3/2/00 -0700, Jamie Gritton wrote: >Khetan Gajjar <khetan@uunet.co.za> 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 was the previous state of the dead plex and it's subdisks? 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"). Only problems I've had when reviving were due to pilot error, so must have stepped right on the bug that was fixed in the recent commits. >> 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. 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. I'd be some of the commits will filter back in a week or 6 (the last MFC). Greg must have been busy. 8-) My last -stable build was 2/4 and changed up to current shortly after that. Anyone else still have the undying vinum process? Should have been fixed on the 2/14 commit, but it recent creeped back into current (at least for me). At least I can no longer force it to panic, but will be testing the recent current commits again. Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.3.32.20000303072732.00989b20>