From owner-freebsd-questions@FreeBSD.ORG Sat May 15 08:18:36 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 B315216A4CE for ; Sat, 15 May 2004 08:18:36 -0700 (PDT) Received: from web40706.mail.yahoo.com (web40706.mail.yahoo.com [66.218.78.163]) by mx1.FreeBSD.org (Postfix) with SMTP id A0BFE43D4C for ; Sat, 15 May 2004 08:18:35 -0700 (PDT) (envelope-from wisco_disco@yahoo.com) Message-ID: <20040515151835.80348.qmail@web40706.mail.yahoo.com> Received: from [24.208.53.234] by web40706.mail.yahoo.com via HTTP; Sat, 15 May 2004 08:18:35 PDT Date: Sat, 15 May 2004 08:18:35 -0700 (PDT) From: Doug Poland To: Greg 'groggy' Lehey In-Reply-To: <20040515033647.GV74538@wantadilla.lemis.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: questions@freebsd.org Subject: Re: Vinum striped volume has corrupt plex, FIXED! X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: doug@polands.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 May 2004 15:18:36 -0000 --- Greg 'groggy' Lehey wrote: > > The error messages I'm seeing are... > > > > vinum: dataraid.p0.s1 is stale by force > > vinum: dataraid.p0 is corrupt > > > > > OK, here your second subdisk has gone stale, meaning that updates > have been missed. There's every reason to believe that the data is > inconsistent, but possibly it's nothing that an fsck couldn't gloss > over. > > In this case, use "setstate": > > # vinum setstate up dataraid.p0.s1 dataraid.p0 > That worked, thanks. If you don't mind, could you point me to some documentation that explains a little more about what setstate does and why? > Then do your fsck--if you want to be cautious, fsck -n in case > something goes seriously wrong--and confirm that you can still access > the file system on the volume. If that's OK, do a > I can see the filesystem but thousands of files have problems. I ran fsck -y and the disk is marked clean and I could mount the filesystem. > # vinum saveconfig > > Until you do the saveconfig, the changes you made with setstate are > only in memory, and unless something else saves the state, they will > be gone on reboot. > OK, that's done too. Upon inspection alot of data is missing from the filesystem. No worries, I have a complete backup from 11 hours before the crash. Many thanks for your help Greg. -- Regards, Doug __________________________________ Do you Yahoo!? SBC Yahoo! - Internet access at a great low price. http://promo.yahoo.com/sbc/