From owner-freebsd-questions@FreeBSD.ORG Mon Aug 23 00:42:19 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12D2216A4CE for ; Mon, 23 Aug 2004 00:42:19 +0000 (GMT) Received: from ozlabs.org (ozlabs.org [203.10.76.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DAFB43D31 for ; Mon, 23 Aug 2004 00:42:18 +0000 (GMT) (envelope-from grog@lemis.com) Received: from blackwater.lemis.com (blackwater.lemis.com [192.109.197.80]) by ozlabs.org (Postfix) with ESMTP id E36012BD43 for ; Mon, 23 Aug 2004 10:42:15 +1000 (EST) Received: by blackwater.lemis.com (Postfix, from userid 1004) id D72DC51202; Mon, 23 Aug 2004 10:12:13 +0930 (CST) Date: Mon, 23 Aug 2004 10:12:13 +0930 From: Greg 'groggy' Lehey To: "Peter A. Giessel" Message-ID: <20040823004213.GX92256@wantadilla.lemis.com> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NJ5+aVN4Egd/eJfU" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: freebsd-questions@freebsd.org Subject: Re: vinum, fsck generates errors when Plex 1 is up X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Aug 2004 00:42:19 -0000 --NJ5+aVN4Egd/eJfU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sunday, 22 August 2004 at 11:35:15 -0800, Peter A. Giessel wrote: > I have two plexes in an array (FreeBSD 5.2.1-RELEASE, which I needed so > that I could run Samba3 with ACL). > > The following is roughly how my array is (was) set up. > volume array > plex org raid5 (p0) > drive one (p0.s0) > drive two (p0.s1) > drive three (p0.s2) > drive four (p0.s3) > drive five (p0.s4) > drive eleven (p0.s5) > plex org raid5 (p1) > drive six (p1.s0) > drive seven (p1.s1) > drive eight (p1.s2) > drive nine (p1.s3) > drive ten (p1.s4) > drive twelve (p1.s5) That's impossible. You can't put plexes on drives; they've got to be on subdisks, which you don't mention. This is why I ask (http://www.vinumvm.org/vinum/how-to-debug.html) for output from vinum(8), which I see you added below: > 2 plexes: > P array.p0 R5 State: up Subdisks: 6 Size: 931 GB > P array.p1 R5 State: faulty Subdisks: 6 Size: 931 GB > > 12 subdisks: > S array.p0.s0 State: up D: one Size: 186 GB > S array.p0.s1 State: up D: two Size: 186 GB > ... > S array.p1.s0 State: stale D: six Size: 186 GB > S array.p1.s1 State: obsolete D: seven Size: 186 GB > ... It would be nice to know when this was done; I assume it was after the successful fsck. Still, to continue... > All was well for a while, then drive twelve failed, so i went to > replace it, created a configfile: > drive twelve device /dev/ad11s1h > > # vinum create configfile > # vinum start array.p1.s5 > > when p1.s5 finished reviving, I got all kinds of fsck errors such > as "INCORRECT BLOCK COUNT", "EXCESSIVE BAD BLOCKS", etc. It would be interesting to know whether this was with the file system mounted and active or not. There have been some race conditions which might cause this problem. If the file system was mounted, could you please try again with it unmounted? If it wasn't, the information in the URL above would helpful. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html Note: I discard all HTML mail unseen. Finger grog@FreeBSD.org for PGP public key. See complete headers for address and phone numbers. --NJ5+aVN4Egd/eJfU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQFBKT1lIubykFB6QiMRArrlAJ9WO5CnmeDqhE+he5GFRnRbQamuGACgim4v rpb8Wxv+PjWOP9O/Kd9+NAo= =ZnS2 -----END PGP SIGNATURE----- --NJ5+aVN4Egd/eJfU--