| Title: | LSM |
| Moderator: | SMURF::SHIDERLY |
| Created: | Mon Jan 17 1994 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 803 |
| Total number of notes: | 2852 |
Hi,
This time my LSM mirrorred /usr filesystem is down due to a power
failure and an intempestive reset of the system after that.
Anyway, whatever is the reason that pushed me in that situation,
I want to change the plex state of one of the plexes to "clean"
in order to be able to start my usrvol volume.
The procedure I know to change the plex state is to use volmend as:
# volmend fix clean usrvol-01
But, ... volmend is in /usr !!! I tried to tar volmend from another
system in my /sbin, but unfortunately it is compiled with shared
libraries which are also in ... /usr !!!
So, my simple but anxious question is :
How can I change the plex state of the /usr volume ??? or
How can I force the usrvol volume to start if no plex is clean ???
And, of course, I never backuped it, the systems being so reliable
nowadays... :-) ---> :-(
Waiting for your helps, guys
Manu.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 780.1 | volmend should run in single-user | SMURF::SCHLOSS | Mon Apr 07 1997 14:30 | 11 | |
What release are you running? In V4.* the volmend command should only
load libc and libvxvm (as reported by "odump -Dl /usr/sbin/volmend").
Both of these libraries reside in root so this shouldn't be a problem.
I will point out that if there were any writes going on at all when
the system crashed then the volume should be recovered by
resynchronizing as there may really be a problem with the plexes being
out of sync. Even if you think that there were no writes going on at
the time it is possible that the system was doing its sync() operation
and some filesystem housekeeping (meta-data or superblocks) blocks were
being flushed.
| |||||
| 780.2 | spoke to soon | SMURF::SCHLOSS | Mon Apr 07 1997 19:12 | 18 | |
Let me try that again. While I stand by my original comment that you
probably don't really want to do that and doing it would leave you at
risk for lots of nasty data corruption problems, you should still be
able to do it. I tried copying volmend to the root filesystem and
running it from single user and ran into the following problem:
# /tmp/volmend
7:/tmp/volmend: /sbin/loader: Fatal Error: cannot map libvxvm.so
The workaround for this is:
# LD_LIBRARY_PATH=/shlib
# export LD_LIBRARY_PATH
# /tmp/volmend
Usage: volmend [-g diskgroup] [-U usetype] [-o useopt] ..........
The problem is that the volmend executable is built to look for its
shared libraries in /usr/shlib. LD_LIBRARY_PATH overrides this.
| |||||
| 780.3 | No way ... | BACHUS::DEVOS | Manu Devos DEC/SI Brussels 856-7539 | Tue Apr 08 1997 09:16 | 11 |
Thanks a lot, Mike, for your time...
But, it appears finally that the LSM mirror of /usr had been removed a
long time ago, for a test and the power cut has damaged my only
remaining plex disk. (It does not spin-up anymore).
So, I decided to re-install my host (fscr44.bro.dec.com) with V4.0B.
I was using V3.2D...
Manu.
| |||||