PROBLEM: (95058, 95147) (PATCH ID: OSF540-227)
********
When using LSM's volclonedg command to clone a LSM disk group whose 
underlying disks have been snapped or cloned in hardware, a new disk group
is created.  If there was a filesystem on one of the LSM volumes in the
parent disk group, we now have a copy of that data.   When trying to mount
the filesystem on the new volume, the vold on another cluster member was
dumping core and the new disk group was deported.   This only occurred when 
smsd was running.   
The problem is smsd queries cluster members for information and may do so from 
each cluster member.  If the cluster member is out of date with respect to 
the LSM configuration, we may get LSM configuration errors.


PROBLEM: (SE_G05218, 95182) (PATCH ID: OSF540-292)
********
This patch prevents vold from core dumping when attempting to delete a
disk that was not initialized properly.
An example stack trace from a core dump follows:
  thread 0x21 signal Segmentation fault at >*[__nxm_thread_kill,
   0x3ff805bab48]   ret     zero, (ra), 1
   (dbx) t
    >  0 __nxm_thread_kill
      1 pthread_kill
      2 (unknown)() [0x3ff805be96c]
      3 (unknown)() [0x3ff807f369c]
      4 exc_raise_signal_exception
      5 (unknown)() [0x3ff805b5a9c]
      6 delete_common
      7 req_da_delete
      8 request_loop()
      9 main(argc = 3, argv = 0x11fffc018)


PROBLEM: (DSATP17S6) (PATCH ID: OSF540-410)
********
This patch fixes a very slow boot when booting several cluster nodes at
the same time and CLSM is configured.