Original Question:
*********************************************
*********************************************
Managers,
I am setting up an Alpha 3000 on DU4.0B with LSM. I have taken an RZ26L
root disk with / and /usr plus a swap partition and encapsulated it with
the volencap utility. No problems.
Now I want to mirror that disk and have the mirror available as a
secondary root disk.
According to the 4.0b documentation on CD, I need to have a disk that is
- not used by LSM (not in LSM database at all or just no partitions
used??)
- at least as big as the root disk
- disklabel with fstypes of unused
I have done all of the above. I ran
(gwen):root# volrootmir -a rz14
ERROR: disk rz1 is an RZ26L type device while
disk rz14 is an RZ26N type device.
Both disks must be of the same type.
The documentation is very clear. I should not have to have the SAME
type of disk - just one at least as big. Thinking that perhaps I had to
edit the disklabel to make partition sizes match, I edited the RZ26N
disklabel, and re-tried only to get the same results.
Do I really have to have another RZ26L, or is there a way around this
problem?
TIA
Susan
susrod_at_hbsi.com
Solution:
***********************************************
***********************************************
Thanks to Idris W Morgan (iwm_at_uvo.dec.com) for the solution:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Due to an over enthusiastic script you have to have the same disk type!
The problem is that the volrootmir script uses file to work out if the
disks are the same. It then compares the bit that says RZ26L with RZ26N
and
says "Not the same".
To workaround this you could modify the volrootmir script thus:
rdtype=`file /dev/r${rootdisk}c | awk '{print $7}' | cut -b 1-4`
ndtype=`file /dev/r${newdisk}c | awk '{print $7}' | cut -b 1-4`
[ "$rdtype" != "$ndtype" ] && {
echo ""
echo " ERROR: disk $rootdisk is an $rdtype type device while"
echo " disk $newdisk is an $ndtype type device."
echo " Both disks must be of the same type."
echo ""
quit 1
}
(This is near the bottom of the file - search for the ERROR message
listed
above.)
regards
iwm
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This worked to get me past that error, however I ran into another one
immediately.
Error message:
Initializing rz14.
The current encapsulation/mirroring process uses a portion of swap
space on the system disk and its mirror to hold the private region.
The length of the swap volume (260142) plus the length of the private
region (1024) is 261166. The target swap partition rz14b (260142) is
not large enough to hold swapvol and the private area.
To mirror the root disk you must increase the size of partition
rz14b by 1024 blocks before running volrootmir.
I had to manually edit the disklabel and calculate the offset on all the
partitions. I would think that volrootmir would do these calculations
since it supposedly copies to root disk's disklabel to the target drive.
It ought to be able to figure the rest out.
Once I edited the disklabel, I was able to successfully mirror my root
drive.
Thanks again,
Susan
susrod_at_hbsi.com
Received on Wed Oct 29 1997 - 02:53:15 NZDT