Hello,

AFAIK only way to remove these paths is reboot as VxDMP cannot clean its 
in-kernel DB. By the way, funny things like hangs/panics can happen if you will 
map new luns to old paths. In 4.1 at least.

On 03.12.2010, at 12:07, Gyula Szekely wrote:

> Hello,
> 
> We have a 2-node cluster with Solaris 9, VxVM version 4.1_p3. There was a 
> storage migration from Hitachi to EMC, and after the Hitachi LUNs were 
> removed the vxdmpadm still indicates the paths to the old disks, in DISABLED 
> state. Is there a way to remove these paths online, without reconfig reboot? 
> Did anyone encountered such a situation and solved it without reboot?
> 
> - cfgadm -al shows only the new disks
> - vxdisk list shows only the new disks
> - format shows only the new disks
> - /dev/vc/[r]dmp is cleaned of devices indicating the old disks
> - /dev/[r]dsk has only the new devices (cleaned with devfsadm)
> - vxconfigd -k has been run (freezed the groups); after vxdctl enable the 
> paths still remained: 
> 
> NAME         STATE[A]   PATH-TYPE[M] DMPNODENAME  ENCLR-TYPE   ENCLR-NAME   
> ATTRS
> ================================================================================
> NONAME       DISABLED     -          NONAME       Disk         Disk           
> -
> NONAME       DISABLED     -          NONAME       Disk         Disk           
> -
> NONAME       DISABLED     -          NONAME       Disk         Disk           
> -
> NONAME       DISABLED     -          NONAME       Disk         Disk           
> -
> NONAME       DISABLED     -          NONAME       Disk         Disk           
> -
> NONAME       DISABLED     -          NONAME       Disk         Disk           
> -
> NONAME       DISABLED     -          NONAME       Disk         Disk           
> -
> NONAME       DISABLED     -          NONAME       Disk         Disk           
> -
> NONAME       DISABLED     -          NONAME       Disk         Disk           
> -
> NONAME       DISABLED     -          NONAME       Disk         Disk           
> -
> NONAME       DISABLED     -          NONAME       Disk         Disk           
> -
> NONAME       DISABLED     -          NONAME       Disk         Disk           
> -
> NONAME       DISABLED     -          NONAME       Disk         Disk           
> -
> NONAME       DISABLED     -          NONAME       Disk         Disk           
> -
> NONAME       DISABLED     -          NONAME       Disk         Disk           
> -
> NONAME       DISABLED     -          NONAME       Disk         Disk           
> -
> NONAME       DISABLED     -          NONAME       Disk         Disk           
> -
> NONAME       DISABLED     -          NONAME       Disk         Disk           
> -
> NONAME       DISABLED     -          NONAME       Disk         Disk           
> -
> NONAME       DISABLED     -          NONAME       Disk         Disk           
> -
> NONAME       DISABLED     -          NONAME       Disk         Disk           
> -
> NONAME       DISABLED     -          NONAME       Disk         Disk           
> -
> NONAME       DISABLED     -          NONAME       Disk         Disk           
> -
> NONAME       DISABLED     -          NONAME       Disk         Disk           
> -
> 
> Thank you in advance,
> Gy.
> 
> PS. there is similar situation also with VxVM version 5.01-MP1
> 
> _______________________________________________
> Veritas-vx maillist  -  [email protected]
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

--
Dmitry Glushenok
Jet Infosystems

_______________________________________________
Veritas-vx maillist  -  [email protected]
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Reply via email to