Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 23 Oct 2001 18:30:23 +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:  <20011023183023.M27668@wantadilla.lemis.com>
In-Reply-To: <20011023044950.A43848@nitrogen.nexthop.net>; from bene@nitrogen.nexthop.net on Tue, Oct 23, 2001 at 04:49:50AM -0400
References:  <20011023044950.A43848@nitrogen.nexthop.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, 23 October 2001 at  4:49:50 -0400, Ben Eisenbraun wrote:
> Howdy-
>
> I'm hoping someone knows if it's possible to recover from a vinum state
> like the one below.  I wedged the NIC somehow and during the reboot,
> the machine paniced while coming up; I rebooted a few more times before
> getting it to single user.
>
> vinum -> list
> 8 drives:
> D max1                  State: up       Device /dev/ad0e        Avail: 19529/19529 MB (100%)
> D max2                  State: up       Device /dev/ad2e        Avail: 19529/19529 MB (100%)
> D wd1                   State: up       Device /dev/ad8e        Avail: 57239/57239 MB (100%)
> D wd2                   State: up       Device /dev/ad10e       Avail: 57239/57239 MB (100%)
> D max3                  State: referenced       Device  Avail: 0/0 MB
> D max4                  State: referenced       Device  Avail: 0/0 MB

Is this information correct (i.e. you have six drives)?

> 2 volumes:
> V stripe-mirror         State: up       Plexes:       2 Size:        111 GB
> V var-mirror            State: up       Plexes:       2 Size:         19 GB
>
> 4 plexes:
> P stripe-mirror.p0    S State: corrupt  Subdisks:     2 Size:        111 GB
> P stripe-mirror.p1    S State: corrupt  Subdisks:     2 Size:        111 GB
> P var-mirror.p0       C State: up       Subdisks:     1 Size:         19 GB
> P var-mirror.p1       C State: up       Subdisks:     1 Size:         19 GB
>
> 6 subdisks:
> S stripe-mirror.p0.s0   State: crashed  PO:        0  B Size:         55 GB
> S stripe-mirror.p0.s1   State: up       PO:      512 kB Size:         55 GB
> S stripe-mirror.p1.s0   State: crashed  PO:        0  B Size:         55 GB
> S stripe-mirror.p1.s1   State: up       PO:      512 kB Size:         55 GB
> S var-mirror.p0.s0      State: up       PO:        0  B Size:         19 GB
> S var-mirror.p1.s0      State: up       PO:        0  B Size:         19 GB
>
> I tried grabbing the requested log info from the vinum slices, but the
> output didn't turn out as expected:
>
> # for i in /dev/ad4s1e /dev/ad6s1e /dev/ad8s1e /dev/ad10s1e ; do
>> (dd if=$i skip=8 count=6|tr -d '\000-\011\200-\377'; echo) >> log
>> done
> 1~^R:/uB
> ^O1u[^_US]^PSu^Lu#9u1^Th^]#h$#V]^LUWVS]=<*u}=*u^Oh 7**j^Pj^P5*{u+hd5*h$=\)T^Yt^ThE#80$^T*<*u1^Z9^]*
> ^O5^T*15$^O^M$^\$!^O=^X$=^P$15x$^M`$>^Md$P5*^Of15x$)5* ^]*0^P*^L*E^LE05))9u^Pvu^PU^PU^O6^MP$^]0^K^?
> <)k)9^P*tI=*u^Oh *5^T*^Md$)P5*^O)^P*C=t$^U*:^K^? C^MP$^M)9w^Ru;)w50$^X5)#58)5@)#5L$9=^L*t*P^Md$P5*S
> ^O=^L*0#8));uvuV*PMQu50)u^OE^Pe[^_^LUWVS=<*^OU=^X*u^Ohx^X*4*jj5^X*^O^]^X*,*w=1zu^W
> uw^KFu^Mt^PFv=,*u,*t#t\{t
> hN#C4*j4*@P5^X*(uy^M^X*9WEVu^LWEVt^P=0*tihT#E=8*u^Wfyu
> $*8*^O^U0*9s^Ou^VhZ#h$#4#4*u^P4*E^LE^LPue[^_^LU^PWVS}u^L%^O^OGst%^?
>
> (I have a feeling this bodes ill.)

Yes.  This drive contains no Vinum label.  Are ad4s1e and ad6s1e the
correct device names?

> The logfile at /var/log/vinum_history contains no relevant info.
>
> I do have copies of the original configuration files, and the "How to
> debug vinum" page mentions that it may be possible to re-create the
> on-disk configuration, but I'm not sure what steps I need to take to
> try this.
>
> I'm guessing I could 'resetconfig', 'create -f my-config-file' and
> then not 'init' the plex, but I thought I would seek advice before
> doing that.

That's a very good idea, to ask advice first.  init writes zeros to
the entire plex, probably not what you want.

> I have a trace from the crash and some other info that spewed on the
> console if it's of interest.

Well, that's what I ask for in "How to debug", along with a lot of
other stuff.  But since your Vinum drives seem to have disappeared,
that's where you need to look first.  What drives do you have on the
system?  If those two I mentioned above are correct, what do their
(Microsoft) partition tables and disk labels look like?  What does
'vinum dumpconfig -v' say?

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?20011023183023.M27668>