Does anyone out there have LSM experience?
What we propose to do is, prior to upgrading from 3.2C to 4.0D we want to
swap disks in LSM volumes from RZ28s ro RZ32s, 2GB to 18GB.
One system is a 2100 ev4 one cpu. The volume in question has only one
subdisk.
# volprint -ht
DG NAME GROUP-ID
DM NAME DEVICE TYPE PRIVLEN PUBLEN PUBPATH
V NAME USETYPE KSTATE STATE LENGTH READPOL PREFPLEX
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT ST-WIDTH
MODE
SD NAME PLEX PLOFFS DISKOFFS LENGTH DISK-NAME DEVICE
dg rootdg 793983486.1025.L01019
dm disk01 re3 sliced 512 4109808 /dev/rre3h
dm disk02 re4 sliced 512 4109808 /dev/rre4h
dm disk03 re5 sliced 512 4109808 /dev/rre5h
dm disk04 re1f simple 512 199488 /dev/rre1f
dm re2 re2 sliced 512 4109808 /dev/rre2h
v cache fsgen ENABLED ACTIVE 4109808 SELECT -
pl pl-02 cache ENABLED ACTIVE 4109808 CONCAT -
RW
sd disk03-01 pl-02 0 0 4109808 disk03 re5
I intend to do the following after physically installing the new drive:-
BACKUP (obviously)
Once the device is available from UNIX, the cache area can be moved from
the old disk to the new disk within LSM. This involves introducing the new
disk, migrating the data, removing the old disk. this may be achieved using
the voldiskadm menu:-
# voldiskadm
>From the menu select option 1 to add/initialise the new disk into LSM.
When complete use option 7 to move the all the volumes (should only be
cache) from the old disk to the newdisk.
Once this is complete option 3 will remove the old disk completely from LSM
control and should leave it available for other use.
On the other node, 2100 4ev5 cpus, the cache volume consists of 4 volumes:-
# volprint -ht
DG NAME GROUP-ID
DM NAME DEVICE TYPE PRIVLEN PUBLEN PUBPATH
V NAME USETYPE KSTATE STATE LENGTH READPOL PREFPLEX
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT ST-WIDTH
MODE
SD NAME PLEX PLOFFS DISKOFFS LENGTH DISK-NAME DEVICE
dg rootdg 758388085.1025.master
dm disk01 re3 sliced 512 4109808 /dev/rre3h
dm disk02 re8 sliced 512 4109808 /dev/rre8h
dm disk03 re9 sliced 512 4109808 /dev/rre9h
dm disk04 re10 sliced 512 4109808 /dev/rre10h
dm disk05 re11 sliced 512 4109808 /dev/rre11h
dm disk06 re12 sliced 512 4109808 /dev/rre12h
dm disk07 re13 sliced 512 4109808 /dev/rre13h
dm disk08 re2e simple 512 1999488 /dev/rre2e
v cache fsgen ENABLED ACTIVE 16439232 SELECT -
pl cache-01 cache ENABLED ACTIVE 16439232 CONCAT -
RW
sd disk04-01 cache-01 0 0 4109808 disk04 re10
sd disk05-01 cache-01 4109808 0 4109808 disk05 re11
sd disk06-01 cache-01 8219616 0 4109808 disk06 re12
sd disk07-01 cache-01 12329424 0 4109808 disk07 re13
do I use the same method as above to replace the old 2GB disk with the new
18GB disk. Does this method increase the volume size by the amount left
over from migrating from the 2GB disk. Is there anything I am missing?
Basically is what I am proposing the correct method of replacing a 2GB
disk in an LSM volume with an 18GB disk, preserving the data.
Do I need to be in single user mode, or is it acceptible to do it in
multiusermode .
Any advice will be most gratefully accepted. (summary to follow) as I have
no experience with LSM and am trudging through the available documentation.
Regards
Mark_Cuthbert_at_yorkshirewater.plc.uk
Received on Wed Nov 11 1998 - 14:31:36 NZDT