SUMMARY: failed LSM configuration copies on disk

From: Willig Reimund <Willig.Reimund_at_gdr.de>
Date: Tue, 09 Feb 1999 15:20:37 +0100

Hello mirrored ones,
thank you Alan for your response, which came immediately and pointed to
right direction:

my question was:

>while testing some features around LSM i noticed a strange behavior,
>which someone might possible explain:
>
>i created a LSM-disk using "voldiskadm rz24" (in fact this is a disk
>originating from an EMC 3700 Box) as a member of a diskgroup called
>"infdg". Then i configured some subdisks out of rz24 to build some
>plexes which were brought up as a mirror for several already existing
>volumes of this diskgroup. Up to this point - including mirroring -
>everything worked as expected.
>Then i deported the mentioned diskgroup using "volplex deport" and all
>the other stuff like stopping the volumes etc. before! Next step was to
>change the scsi-controller to which the rz24 disk was connected, so it
>came up as rz16 after a reboot. After giving a "voldisk define rz16" and
>a following "volplex import", LSM complained that no configuration
>records could be found on disk! A "voldisk list rz16" made clear that
>the configration copies were missing! Why?
>
># voldisk list rzc16
>Device: rzc16
>devicetag: rzc16
>type: sliced
>hostid:
>disk: name= id=918213924.1799.didg12
>group: name=infdg id=894977025.1043.didg12
>flags: online ready private
>pubpaths: block=/dev/rzc16g char=/dev/rrzc16g
>privpaths: block=/dev/rzc16h char=/dev/rrzc16h
>version: 1.1
>iosize: 512
>public: slice=6 offset=16 len=17676400
>private: slice=7 offset=0 len=1024
>update: time=918478648 seqno=0.20
>headers: 0 248
>configs: count=0 len=0
>logs: count=0 len=0


the solution is:
If you already have 8 disks in a diskgroup, voldiskadm
will set the config copies to 0 on any new disks.

here is workaround:

 (via Dsn_Mail V2.3; sender davis_at_petey.2122868.dsn)

[LSM] HowTo:Correct or Increase the Number of Configuration Copies

     Any party granted access to the following copyrighted information
     (protected under Federal Copyright Laws), pursuant to a duly
executed
     Compaq Service Agreement may, under the terms of such agreement
copy
     all or selected portions of this information for internal use and
     distribution only. No other copying or distribution for any other
     purpose is authorized.

Last Technical Review Date: Sun Nov 15 19:00:00 1998
Size: 88 lines.



) Copyright Compaq Computer Corporation 1998. All rights reserved.


COMPONENT: LSM

OPERATING SYSTEM OR PRODUCT NAME: Compaq's Digital UNIX

VERSION: V4.0 and higher

DESCRIPTION OF TASK OR ACTIVITY:

Increase the number of config copies on a disk. This is the opposite
of the operation:
     # voldisk moddb <dm> nconfig=0




HOWTO PERFORM THE DESIRED TASK OR ACTIVITY:

Check the parameters of the private area for this disk :

     # voldisk list <dm>

Note the privlen parameter.

Remove the disks from LSM control so we can manipulate them,
but leave the dg record to connect to, when we are done.

      # voldg -g dg -k rmdisk <da>
      # voldisk rm <dm>

At this point, if the volume has only one plex, it is inaccessible
to users.

Rewrite the private area on the disk and bring it into LSM:

     # voldisksetup -i <dm> nconfig=N nlogs=Y privlen=Z

Where:
      N is the new number of config copies for this disk
      Y is the new number of logs
      Z is the privlen for this volume : MUST BE THE SAME AS
        ORIGINAL or you risk losing data.

Reassociate the device to the disk access name and the diskgroup.

     # voldg -g <dg> -k adddisk <da>=<dm>

At this point, the volume will be disabled and clean, and the plex
will be disabled and recovered.
To bring the volume back online do:

     # volmend fix stale <pl>
     # volmend fix active <pl>
     # volrecover -sb <v>

Symbol definitions:

  v = volume
  pl = plex
  dm = disk media name (unix device spec)
  da = disk access name (lsm disk name, recommendation = do not use
       UNIX device spec)

These are the acronyms documented in the LSM manuals. The
volprint and voldisk output uses the following:

voldisk list, voldg :
DEVICE = dm = unix device spec
DISK = da = lsm disk name

volprint :
DEVICE = dm = unix device spec
NAME = da = lsm disk name


 




 mit freundlichen Gruessen
          Reimund Willig
------------------------------------------
e-mail: willig.reimund_at_gdr.de
       tel: +49-5205-941747
      fax: +49-5205-941725
  ** Schwer ist leicht was **
-----------------------------------------
Received on Tue Feb 09 1999 - 14:22:20 NZDT

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