From owner-freebsd-questions Fri Dec 8 16:34:18 2000 From owner-freebsd-questions@FreeBSD.ORG Fri Dec 8 16:34:16 2000 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 43ABF37B400 for ; Fri, 8 Dec 2000 16:34:14 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 0AC7A6AB68; Sat, 9 Dec 2000 11:04:11 +1030 (CST) Date: Sat, 9 Dec 2000 11:04:10 +1030 From: Greg Lehey To: Dan Langille Cc: freebsd-questions@FreeBSD.ORG Subject: Re: stale/corrupt vinum volumes Message-ID: <20001209110410.F53111@wantadilla.lemis.com> References: <200012080150.OAA33830@ducky.nz.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200012080150.OAA33830@ducky.nz.freebsd.org>; from dan@langille.org on Fri, Dec 08, 2000 at 02:49:52PM +1300 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 8 December 2000 at 14:49:52 +1300, Dan Langille wrote: > I'm running FreeBSD 3.3-19991207-SNAP and I noticed this earlier today: > > Dec 8 12:28:53 fred /kernel: nzmirror.p0.s1: fatal write I/O error > Dec 8 12:28:53 fred /kernel: vinum: nzmirror.p0.s1 is stale by force > Dec 8 12:28:53 fred /kernel: vinum: nzmirror.p0 is corrupt > Dec 8 12:29:53 fred /kernel: nzmirror.p0.s1: fatal write I/O error > > then > > Dec 8 12:31:23 fred /kernel: vinum: drive d2 is down > Dec 8 12:31:24 fred /kernel: vinum: Can't write config to /dev/da2s1e, error 5 > Dec 8 12:31:24 fred /kernel: (da2:ncr0:0:4:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 > Dec 8 12:31:24 fred /kernel: (da2:ncr0:0:4:0): NOT READY asc:4,0 > Dec 8 12:31:24 fred /kernel: (da2:ncr0:0:4:0): Logical unit not ready, cause not reportable > > Below are some other observations. Everything on the drives can be recovered > (its cvsup.nz.freebsd.org), but I'd rather not do that until I can source some > replacement drives. Right, it looks as if a drive has died. The system seems to have handled the situation correctly, but since you only have one plex, you've effectively lost the volume, though you can access bits of it. Did you have a question? I don't see one. Greg > D d1 State: up Device /dev/da1s1e Avail: 0/1001 MB (0%) > D d2 State: up Device /dev/da2s1e Avail: 0/1001 MB (0%) If you're wondering why d2 is shown as "up", it's because you got a write error, not a "device not present" error. That's also what you get when only part of the drive is inaccessible, so it's not appropriate to mark the drive down. > V nzmirror State: up Plexes: 1 Size: 2002 MB > > P nzmirror.p0 S State: corrupt Subdisks: 2 Size: 2002 MB > > S nzmirror.p0.s0 State: up PO: 0 B Size: 1001 MB > S nzmirror.p0.s1 State: stale PO: 256 kB Size: 1001 MB > > [root@fred:/usr/local/www] # camcontrol devlist > at scbus0 target 0 lun 0 (pass0,da0) > at scbus0 target 2 lun 0 (pass1,da1) > at scbus0 target 4 lun 0 (pass2,da2) > at scbus0 target 6 lun 0 (pass3,cd0) I think a 'camcontrol rescan' would remove da2. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply. For more information, see http://www.lemis.com/questions.html Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message