Forum Discussion

sandy321's avatar
sandy321
Level 4
14 years ago

VxVM vxdisksetup ERROR V-5-2-3535 c1t2d0s2: Invalid dmpnodename for disk device c1t2d0.

 # vxdisk list | grep -i disk_1 Disk_1       auto:none       -            -            online invalid    # vxdisk -e list | grep -i disk_1 Disk_1       auto      -             -           ...
business continuity
Clustering
High availability
Storage Foundation
  • Gaurav_S's avatar
    Gaurav_S
    14 years ago

    you have to use Disk_1 instead of cxtxdx name..

     

    # vxdisksetup -i Disk_1

    Veritas understands Disk Access names i.e Disk_1 for c1t2d0s2

     

    Gaurav

g_lee's avatar
g_lee
Level 6
14 years ago

Assuming you're referring to the output from before you initialised the disk - the disk shows online in both vxdisk list and vxdisk -e list as this means VxVM can see the disk / has access to the disk.

The vxdisk list also shows an additional state of "invalid" meaning it was not a VxVM disk / had not been initialised by VxVM / did not have a VxVM private region. The vxdisk -e list does not have this additional status (presumably to save space, as it already has an additional column to display the OS path to the disk).

Once you have initialised the disk, vxdisk list should still show online, but will no longer show "invalid" as the disk has now been initialised / can be used by VxVM.