| 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 |
Hello all,
I have what may be a unique situation. My customer has an 8400 at 3.2G
with root and /usr as mirrored advfs volumes. He wants to upgrade to 4.0B
in an unusual manner: He wishes to break the mirror on root & /usr, upgrade
one of the plexes, see how things look, then bring the mirror back online.
If he does not like it, he will boot the old 3.2G plex, and re-mirror back
the old way.
Is this doable? Here's some of the configuration information. I'll be happy
to supply any futher data.
# cat /etc/fstab
root_domain#root / advfs rw 0 0
/proc /proc procfs rw 0 0
usr_domain#usr /usr advfs rw 0 0
/dev/vol/rootdg/swapvol swap1 ufs sw 0 2
/dev/vol/rootdg/volswap swap2 ufs sw 0 2
[Output of relevant ls -lR:]
/etc/fdmns/root_domain:
total 0
lrwxrwxrwx 1 root system 23 Aug 27 1996 rootvol ->
/dev/vol/rootdg/rootvol
/etc/fdmns/usr_domain:
total 0
lrwxrwxrwx 1 root system 24 Aug 27 1996 rz41g ->
/dev/vol/rootdg/volrz41g
[Relevant output of volprint]
vol volrz41g gen ENABLED 8093360
plex volrz41g-01 volrz41g ENABLED 8093360
sd advfs_rz41g-01 volrz41g-01 - 8093360
plex volrz41g-02 volrz41g ENABLED 8093360
sd rz81g-01 volrz41g-02 - 8093360
vol rootvol root ENABLED 262144
plex rootvol-01 rootvol ENABLED 262144
sd rz41-01 rootvol-01 - 16
sd rz41-02 rootvol-01 - 262128
plex rootvol-02 rootvol ENABLED 262144
sd rz81-01 rootvol-02 - 16
sd rz81-02 rootvol-02 - 262128
[Posted by WWW Notes gateway]
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 759.1 | Not supported but might be doable | SMURF::SCHLOSS | Wed Feb 26 1997 16:17 | 33 | |
The simple answer is no, this is not supported.
A more complicated answer is that there may be a way to do this but it
is not easy nor is it guarenteed to work. One posible procedure would
be as follows:
1) use "voldisk moddb" to disable config databases on all disks
except the two bootable disks.
2) shut the system down cleanly.
3) Physically disable one of the bootable disks (disconnect it from
the SCSI bus).
4) Reboot the machine.
5) Install 4.0B. This may entail run volunroot, upgrading, and
rerunning volencap.
6a) If it looks good then reconnect the backup disk, relabel the
disk, and run volrootmir.
6b) If it doesn't look good then shut the machine down, pull the
new boot disk, reinsert the old boot disk, and boot off the old
boot disk. When the system comes up you can remove the LSM
configuration entries for the "new" disk and then reinsert the
disconnected disk. You can then relabel the "new" disk and run
volrootmir.
7) You now should make sure that there are sufficient config
databases available. You may need to remove and re-add disks.
Good Luck
| |||||