From owner-freebsd-questions Thu Mar 21 15:50:47 2002 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 8455A37B400 for ; Thu, 21 Mar 2002 15:50:40 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id BFFCE78340; Fri, 22 Mar 2002 10:20:37 +1030 (CST) Date: Fri, 22 Mar 2002 10:20:37 +1030 From: Greg 'groggy' Lehey To: Kris Kirby Cc: freebsd-questions@freebsd.org Subject: Re: Vinum, "stale" disk. Message-ID: <20020322102037.G69857@wantadilla.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23i 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: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thursday, 21 March 2002 at 16:25:52 +0000, Kris Kirby wrote: > > # vinum l > > 3 drives: > D a State: up Device /dev/ad1s1e Avail: 1/19469 MB (0%) > D b State: up Device /dev/ad2s1e Avail: 1/19469 MB (0%) > D c State: up Device /dev/ad3s1e Avail: 1/19469 MB (0%) > > 1 volumes: > V raid0 State: up Plexes: 1 Size: 38 GB > > 1 plexes: > P raid0.p0 R5 State: degraded Subdisks: 3 Size: 38 GB > > 3 subdisks: > S raid0.p0.s0 State: up PO: 0 B Size: 19 GB > S raid0.p0.s1 State: stale PO: 273 kB Size: 19 GB > S raid0.p0.s2 State: up PO: 546 kB Size: 19 GB > > #uname -a > FreeBSD kickme.huntsvilleal.com 4.3-STABLE FreeBSD 4.3-STABLE #0: Fri May 4 02:14:02 GMT 2001 root@kickme.huntsvilleal.com:/usr/src/sys/compile/TUCOWS i386 > > How can I force vinum to update drive .s1 without comprimising the > integrety of the data on the other two drives? The simple answer: you can't. This is a non-resilient configuration, and it's no longer consistent. The more complicated answer: use these commands: # vinum setstate up raid0.p0 raid0.p0.s1 # vinum saveconfig Depending on how the subdisk went down, you may or may not have a usable file system. This would be the configuration you'd have if you replaced drive b, for example. You're telling Vinum that there's data on raid0.p0.s1 when in fact there isn't. 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 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