Date: Sat, 15 May 2004 13:06:47 +0930 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: Doug Poland <djp@polands.org> Cc: questions@freebsd.org Subject: Re: Vinum striped volume has corrupt plex, please help Message-ID: <20040515033647.GV74538@wantadilla.lemis.com> In-Reply-To: <200405150122.i4F1MblG013038@galilee.polands.org> References: <200405150122.i4F1MblG013038@galilee.polands.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--EyuBRJR0MsVMWKTf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Friday, 14 May 2004 at 20:22:37 -0500, Doug Poland wrote: > Hello, > > I've been running a striped vinum configuration on 7 2.1GB SCSI drives > for almost three years. I recently returned from a vacation to find my > vinum fileserver had crashed. The logs indicated some type of problem > with my Adaptec 2940AU host adapter. The 2940 seems be working now but > now I'm having a problem with my vinum volume. > > The error messages I'm seeing are... > > vinum: dataraid.p0.s1 is stale by force > vinum: dataraid.p0 is corrupt > > I've spent no small amount of time searching the web google, and > newsgroups. From what I've found I think I should be able to run a > vinum create and the volume will re-build. But before I do that, I was > hoping to get confirmation that my procedure would work. No, that's a bad idea. > In accordance with the instructions found at > http://www.vinumvm.org/vinum/how-to-debug.html, I'm including the > requested information as follows: Thank you! > Problem: Corrupt plex > > 1 plexes: > P dataraid.p0 S State: corrupt Subdisks: 7 Size: 13 GB > > 7 subdisks: > S dataraid.p0.s0 State: up PO: 0 B Size: 1920 MB > S dataraid.p0.s1 State: stale PO: 256 kB Size: 1920 MB > S dataraid.p0.s2 State: up PO: 512 kB Size: 1920 MB > S dataraid.p0.s3 State: up PO: 768 kB Size: 1920 MB > S dataraid.p0.s4 State: up PO: 1024 kB Size: 1920 MB > S dataraid.p0.s5 State: up PO: 1280 kB Size: 1920 MB > S dataraid.p0.s6 State: up PO: 1536 kB Size: 1920 MB 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 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 # 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. 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. --EyuBRJR0MsVMWKTf Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQFApZBPIubykFB6QiMRAgTvAJwJKv6ij0l6B+hYXknrQbHkOc9ZIACeKtTd 7IqWCNT8cdlHjCiMPvdEhRs= =l1Xl -----END PGP SIGNATURE----- --EyuBRJR0MsVMWKTf--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040515033647.GV74538>