From owner-freebsd-questions Wed Jul 21 5:27: 8 1999 Delivered-To: freebsd-questions@freebsd.org Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by hub.freebsd.org (Postfix) with ESMTP id E00341549B; Wed, 21 Jul 1999 05:26:38 -0700 (PDT) (envelope-from marck@rinet.ru) Received: from localhost (marck@localhost) by woozle.rinet.ru (8.9.3/8.9.1) with SMTP id QAA18574; Wed, 21 Jul 1999 16:26:04 +0400 (MSD) Date: Wed, 21 Jul 1999 16:26:04 +0400 (MSD) From: Dmitry Morozovsky To: fs@freebsd.org Cc: questions@freebsd.org, grog@lemis.com Subject: Recovering corrupt vinum FS Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello there, and happy FreeBSDing. We have 3.2-STABLE from 19 of June, with concatenated vinum partition. Some days ago, after kernel panicing and rebooting, vinum refuses to go up. vinum list shows the plex is corrupt, and one of the drives in it is stale state. fsck'ing volume produces LOTS of errors, and does not recover any of them. Can we do something except vinum resetconfig? Sincerely, D.Marck [DM5020, DM268-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message