Just do vxdisk rm name on each of the ghost devices and check. VxVM
sometimes keeps records of disks it has seen in the past
With regards
Hari
-Original Message-
From: veritas-vx-boun...@mailman.eng.auburn.edu
[mailto:veritas-vx-boun...@mailman.eng.auburn.edu] On Behalf Of
If the pathtype is not specified then its an Active/Active LUN. If the pathtype
is specified then its an Active/Passive or Asymmetric Active/Active [ALUA] LUN.
All primary paths would be shown with pathtype as 'primary' and same is the
case with 'secondary' paths.
With regards
Hari
Hi,
VxVM 5.0MP3 onwards has this facility of removing stale device paths from the
DMP kernel database. Prior to this release DMP reatined the information of
stale device paths until the next reboot.
With regards
Hari
--
Hi,
If you are operating on VxVM 5.0MP3 or later and shift to Enclosure
based naming scheme then you should have consistent names across
different nodes of a cluster.
Incase you have some historic device name information which may be
preventing the names from being consistent on all the nodes,
Hi,
This issue of use_all_paths not distributing I/O all paths of an ALUA
array had been identified and fixed internally. The fix should be
available in the subsequent RPs on VRTSvxvm 5.0MP3
With regards
Hari
--
Message: 1
Yes DMP devices are /dev/vx/[r]dmp/*
block=/dev/vx/dmp/c7t500A098186783720d25s2
char=/dev/vx/rdmp/c7t500A098186783720d25s2
With regards
Hari
On Fri, Mar 20, 2009 at 3:46 PM, Sebastien DAUBIGNE
sebastien.daubi...@atosorigin.com wrote:
Theses are the paths through DMP (instead of /dev/dsk
I guess in your case the name persistence was turned on and hence DMP
honoured it and used the name it had chosen previously. In order to set
the names right, you can execute the following VxVM 5.0MP3 command on
server B to get the names aligned with server A
vxddladm assign names
Please
