VINUM Disaster Recovery

[orville weyrich]

I have a 10 disk VINUM configuration and two of the
disks are trashed.  In theory there is still enough
redundant information to get things working again
without data loss.

Vinum has detected a configuration error (duh -- two
disks are toast, plus in recovery I accidently created
two more plexes) and taken upon itself to stop
configuration updates to prevent any further
corruption (thanks! :-).

At this point I have looked at
http://www.vinumvm.org/vinum/how-to-debug.html and
have run a command like the following:

( dd if=/dev/da9s1e skip=8 count=50 | tr -d
'\000-\011\200-\377' ; echo ) > da9s1e.log 

on all 10 disks to obtain a file containing each
disk's on-disk configuration.  As hoped, eight of the
disks show an output similar to the attached file
da1s1e.log (differing only as expected in the first
line).

See attached flog file for a sample output.

PLEASE HELP CONFIRM MY PLAN (FOLLOWING) FOR PROCEEDING
-- I DO NOT WANT TO DO ANYTHING DISASTEROUS.

My thought is that I need to turn on updates, then
delete the two unwanted plexes raid.p2 and
raid.p3(which were accidentally created), detach the
corrupt sdisks, and then hopefully VINUM will forget
about the two disks that are toast (or do I somehow
have to tell VINUM to forget the disks?).

My plan is as follows:

First, selectively start vinum:

vinum -> read /dev/da1s1e /dev/da2s1e /dev/da3s1e
/dev/da4s1e /dev/da5s1e /dev/da6s1e /dev/da7s1e
/dev/da8s1e

Second, enable configuration updates:

vinum->setdaemon 0

Third, save the configuration:

vinum->saveconfig

Fourth, stop and remove the two unwanted plexes and
all attached subdisks:

vinum->stop -f raid.p3
vinum->stop -f raid.p2
vinum->rm -r raid.p3
vinum->rm -r raid.p2

Fifth, stop and detach the corruped subdisks:

vinum->stop -f raid.p0.s0
vinum->stop -f raid.p0.s9
vinum->stop -f raid.p1.s4
vinum->stop -f raid.p1.s5

vinum->detach raid.p0.s0
vinum->detach raid.p0.s9
vinum->detach raid.p1.s4
vinum->detach raid.p1.s5


At this point I expect to have a functional volume
that can be mounted and backed up, prior to the next
step of reinstalling the crashed disks, creating new
subdisks, attaching them to the plexes, and
resynching. 

PLEASE CONFIRM MY APPROACH OR TELL ME WHERE I AM
WRONG!

Thanks

orville








__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: da1s1e.log
Type: application/octet-stream
Size: 4589 bytes
Desc: da1s1e.log
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20041205/cee64345/da1s1e.obj