The error condition originally described (and repeated below) was "fixed"
by rebooting. Upon reboot, the file system mounted just fine and the
volume was back to normal state (no data lost).
Problem:
In the process of rebuilding the metadata for our six volume advfs domain a
rmvol apparently failed (the rmvol was started and is no longer running, so
our guess is it abnormally terminated at some undetermined point). Now,
when we try to balance, defragment, showfile, etc, we get a "set vol params
error EBAD_VDI (-1030)". Doing a showfdmn for the domain yields:
Id Date Created LogPgs Domain Name
2fba3e81.000b1480 Wed May 17 11:20:49 1995 512 users
Vol 512-Blks Free % Used Cmode Rblks Wblks Vol Name
1 8380080 1199776 86% on 128 128 /dev/rz12c
2 8380080 1239328 85% on 128 128 /dev/rz11c
-data unavailable- on 128 128 /dev/rz10c
4 8380080 1209184 86% on 128 128 /dev/rz9c
5 4110480 2971776 28% on 128 128 /dev/rz4c
6 8380080 1263632 85% on 128 128 /dev/rz13c
8L 8380080 1309984 84% on 128 128 /dev/rz14c
and showfile -x M-18 produces:
showfile: get vol params error EBAD_VDI (-1030)
Id Vol PgSz Pages XtntType Segs SegSz Log Perf File
ffffffee.0000 3 16 10626 simple ** ** ftx 100% M-18
extentMap: 1
pageOff pageCnt vol volBlock blockCnt
0 2 3 32 32
2 128 3 1728 2048
130 128 3 1272832 2048
258 128 3 1719088 2048
386 128 3 2164352 2048
514 128 3 2488848 2048
642 128 3 2815104 2048
.....
10498 128 3 6544736 2048
extentCnt: 84
We've gotten some suggestions from Dec for recovering from this (do another
rmvol, advscan, manually remove the volume), but are feeling a bit queasy.
Has anyone recovered from a similar situation or have some helpful hints or
tips? Thanks.
--Diane
Received on Wed Jul 02 1997 - 17:58:34 NZST