SUMMARY: Adding disks in LSM to DU40b

From: LES MAYEDA TECH SUPPORT/ISS X6656 <MAYEDA_at_CSMC.EDU>
Date: Thu, 29 May 1997 12:28:36 -0700 (PDT)

My thanks to Alan from Digital Support (Atlanta):

According to Alan, the problem is related to the SCSI bus
holding the devices which is preventing LSM on systemB (DU40b)
from accessing them.

His solution:

from systemA (du32c) - voldg deport test_dg
                       voldisk rm rz18
                       scu -f /dev/rrz18c release device

from systemB (du40b) - voldisk define rz18
                       voldg import test_dg
                       volume start test_vol
                       volprint -Aht (to check)
                       You may need to make the soft link if using Advfs
                       in /etc/fdmns.

It worked!

Thanks again Alan.

Les Mayeda
mayeda_at_csmc.edu




Original question:
--------------------------------------

Hello,

I am in the process of upgrading our DU3.2c systems (systemA, systemB)
to DU4.0b, under LSM, and in a DecSafe environment.


I have broken apart the DecSafe members and have installed
DU40b (upgrade install) and Trucluster Avail Server on 'systemB'.

I then stopped a Disk Service (test_service) on DU32c (systemA),
deported the disk group (test_dg) and varied offline the disk
associated with the disk group (rz18).

Then on systemB (DU40b), I did: voldiskadd rz18
                                 voldisk online rz18
                                 voldg import test_dg
                                 voldisk -Aht

Everything works except that I don't see the vol info
for the disk group.

How can I add the vol information for this disk group?
               
Once I can get the disk group online manually I will add it
into TruCluster Avail Server later.

Thanks,

Les Mayeda
Cedars-Sinai Medical Center
mayeda_at_csmc.edu



------------------------------

# voldiskadd rz18


Add or initialize a disk
Menu: LogicalStorageManager/Disk/AddDisk

...

  Disk device rz18 appears to have been initialized already.
  The disk is listed as added to disk group test_dg, but is not
  currently active.

Do you wish to use this device? [y,n,q,?] (default: y) y

Do you wish to reinitialize rz18? [y,n,q,?] (default: y) y

...

Which disk group [<group>,none,list,q,?] (default: rootdg) test_dg

...

Enter disk name [<name>,q,?] (default: sirsidg01) rz18

  The requested operation is to initialize disk device rz26 and
  to add this device to disk group sirsidg as disk rz26.

Continue with operation? [y,n,q,?] (default: y) y

Initialize a disk
Menu: LogicalStorageManager/Disk/AddDisk


  Disk initialization for rz18 completed successfully.

Goodbye.

# voldisk list
DEVICE TYPE DISK GROUP STATUS
...
rz18 sliced rz18 test_dg online
...


#voldisk online rz18
#voldg import test_dg

# voldg list
NAME STATE ID
rootdg enabled 789603877.1025.xxx.host.com
...
test_dg enabled 864297299.3073.xxx.host.com


#volprint -Aht
...

Disk group: test_dg

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 test_dg 864297299.3073.xxx.host.com

dm rz18 rz18 sliced 1024 4108430 /dev/rrz18g

...
Received on Thu May 29 1997 - 21:44:34 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:36 NZDT