Date: Fri, 26 Oct 2001 16:54:32 +0930 From: Greg Lehey <grog@FreeBSD.org> To: Ben Eisenbraun <bene@nitrogen.nexthop.net> Cc: freebsd-questions@FreeBSD.org Subject: Re: recovery of corrupt vinum plexes? Message-ID: <20011026165431.C5304@wantadilla.lemis.com> In-Reply-To: <20011025235323.E64298@nitrogen.nexthop.net>; from bene@nitrogen.nexthop.net on Thu, Oct 25, 2001 at 11:53:23PM -0400 References: <20011023044950.A43848@nitrogen.nexthop.net> <20011023183023.M27668@wantadilla.lemis.com> <20011023055005.A44324@nitrogen.nexthop.net> <20011025103000.A25441@wantadilla.lemis.com> <20011025023359.D64298@nitrogen.nexthop.net> <20011026091455.A4706@wantadilla.lemis.com> <20011025235323.E64298@nitrogen.nexthop.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, 25 October 2001 at 23:53:23 -0400, Ben Eisenbraun wrote: > On Fri, Oct 26, 2001 at 09:14:55AM +0930, Greg Lehey wrote: >> On Thursday, 25 October 2001 at 2:33:59 -0400, Ben Eisenbraun wrote: >>> >>> I think I can reproduce this if I frob with it enough, but this >>> kernel wasn't build with debug symbols, and the system sources have >>> been recently updated, so I'm not sure if this would be useful. Do >>> you have any suggestions? >> >> I'd need the debug output. I won't find it otherwise. > > Given the above info, is there a way I can get that? I'm under the > impression that the kernel had to be built with either "makeoptions > DEBUG=-g" or 'config -g MYKERNEL' in order for a crash dump to > be useful. > > I tend to cvsup and then buildworld/kernel directly > afterwards, so I could cvsup with the date for the currently > running kernel and try building a debug kernel. From what I gather > by reading the Developer's Handbook, this might work provided the > sizes of the kernels match. You'd be better off building a new kernel and booting it. Anything else is too haphazard. > Okay, here's the 'vinum setstate up' and 'fsck -n' output: > > vinum -> setstate up stripe-mirror.p0 stripe-mirror.p0.s1 stripe-mirror.p1 stripe-mirror.p1.s1 > stripe-mirror.p0.s1 is already up > stripe-mirror.p1.s1 is already up Oops, you want to bring .s0 up, not .s1. My typo, probably. > root@whiskey [19:56:10][~]>> fsck -n /dev/vinum/plex/stripe-mirror.p0 > ** /dev/vinum/plex/stripe-mirror.p0 (NO WRITE) > > CANNOT READ: BLK 16 > CONTINUE? yes > > THE FOLLOWING DISK SECTORS COULD NOT BE READ: 16, 17, 18, 19, 20, 21, 22, 23, 24 > , 25, 26, 27, 28, 29, 30, 31, > /dev/vinum/plex/stripe-mirror.p0: INCOMPLETE LABEL: type 4.2BSD fsize 1024, frag > 8, cpg 0, size 234450944 Yes, that's a direct result. Your 'vinum list' should show all objects up. Try 'setstate up' again with the subdisks which are still down. 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011026165431.C5304>