Date: Wed, 21 Jul 1999 22:12:07 +0930 From: Greg Lehey <grog@lemis.com> To: Dmitry Morozovsky <marck@rinet.ru> Cc: FreeBSD Questions <questions@FreeBSD.org> Subject: Re: Recovering corrupt vinum FS Message-ID: <19990721221207.X84734@freebie.lemis.com> In-Reply-To: <Pine.BSF.3.96.990721162138.15745A-100000@woozle.rinet.ru>; from Dmitry Morozovsky on Wed, Jul 21, 1999 at 04:26:04PM %2B0400 References: <Pine.BSF.3.96.990721162138.15745A-100000@woozle.rinet.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, 21 July 1999 at 16:26:04 +0400, Dmitry Morozovsky wrote: > 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? Read the manual. 'vinum start' should fix this. If it doesn't, please supply more details, such as the output of 'vinum list'. It would also be interesting to know what the cause of the panic was. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990721221207.X84734>