From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 00:21:51 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5330516A4CE; Wed, 19 Jan 2005 00:21:51 +0000 (GMT) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E64A43D46; Wed, 19 Jan 2005 00:21:51 +0000 (GMT) (envelope-from craig@feniz.gank.org) Received: by ion.gank.org (mail, from userid 1001) id C878A2A98B; Tue, 18 Jan 2005 18:21:50 -0600 (CST) Date: Tue, 18 Jan 2005 18:21:48 -0600 From: Craig Boston To: Greg 'groggy' Lehey Message-ID: <20050119002148.GA1328@nowhere> Mail-Followup-To: Craig Boston , Greg 'groggy' Lehey , David Elsing , freebsd-stable@freebsd.org References: <20050118143302.GA99345@nowhere> <20050118232525.GW79181@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050118232525.GW79181@wantadilla.lemis.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-stable@freebsd.org cc: David Elsing Subject: Re: Vinum Raid5 Init question X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2005 00:21:51 -0000 On Wed, Jan 19, 2005 at 09:55:25AM +1030, Greg 'groggy' Lehey wrote: > Yes, it could be clearer. Put in a PR. I'm more than willing to submit a patch if it will help, but will it do any good this late in the release cycle? Especially if there will be no 4.12 release. > > Also, if a good disk gets marked as "down" somehow before you can > > correct this, whatever you do, do NOT issue a "vinum start" command > > on it. In the current state of the array, that would be destructive > > and irreversible. > > No, that's the correct way to do it. Normally it would be, yes. However in this case (at least it was for me), all of the normal blocks are fine, but the parity blocks are random garbage since init was never run. If a drive goes into the "down" state for some reason but is physically fine, starting the subdisk will begin "reconstructing" the data from the bogus parity, wiping out any hope of recovering the good data. If a drive does get detached somehow, it's likely that the system won't stay up very long -- from its point of view at least one filesystem has suddenly become very corrupt. The setstate is dangerous and will probably result in a somewhat inconsistent filesystem, but it's still preferable to a total loss... > I can't recall seeing a problem report. There wasn't one. I had encountered the problem on several machines in a short timespan (fortunately only one had anything important) so I asked you about in in private mail. I didn't think the problem was with FreeBSD or vinum itself -- it was more of a "what am I doing wrong?" question. After a couple rounds you determined that it was likely I hadn't run vinum init, and sure enough that's what it was. Sorry, I can't provide a time reference. At the time of the exchange my mail archive was down (that's what was on the doomed filesystem :). Craig