Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

vxdisk list shows Simple type disks as "error"

Created: 06 Jan 2014 | 28 comments

Hi ,

Am facing issue on Aix 7 with VxVm

  VRTSvxvm  6.0.300.0    A     F    Veritas Volume Manager by and am  using the Third party Multipathing software (Dynapath).

Problem is that after the "vxdisk scandisk" vxdisk list is showing the foriegn disk in "error " state.Please suggest a way.

 

Steps:

- creating nodes in /dev/vx/dmp, /dev/vx/rdmp

- Added as foreign disk

- vxdisk scandisks

-vxdctl enable

-vxdisk list

   bash-3.2# vxdisk list

DEVICE       TYPE            DISK         GROUP        STATUS
hdisk0       auto:LVM        -            -            LVM
hdiskdpd0    simple          -            -            error
hdisk1       auto:LVM        -            -            LVM
hdisk3       auto:LVM        -            -            LVM
hdisk4       auto:none       -            -            online invalid
hdisk5       auto:LVM        -            -            LVM
 
 
bash-3.2# vxdisk list hdiskdpd0
Device:    hdiskdpd0
devicetag: hdiskdpd0
type:      simple
flags:     error private foreign
pubpaths:  block=/dev/hdiskdpd0 char=/dev/rhdiskdpd0
guid:      -
udid:      INVALID
site:      -
errno:     Device path not valid
 
 
 
 

    

Operating Systems:

Comments 28 CommentsJump to latest comment

Gaurav Sangamnerkar's picture

Hi,

is this a new setup or existing environment was upgraded to 6.0 ?

Did you look at dmp_native_support tunable ? is it set to on ?

refer below

https://sort.symantec.com/public/documents/sfha/6....

From above section

Devices that are multi-pathed with Third-party drivers (TPD)

If a disk is already multi-pathed with a third-party driver (TPD), DMP does not manage the devices unless you remove TPD support. After removing TPD support, turn on the dmp_native_support tunable to migrate the devices.

If LVM volume groups are constructed over TPD devices, then perform the steps to migrate the LVM volume groups onto DMP devices.

To turn on the dmp_native_support tunable, use the following command:

# vxdmpadm settune dmp_native_support=on

The first time this operation is performed, the command reports if a volume group is in use, and does not migrate those devices. To migrate the volume group onto DMP, stop the volume group. Then execute the vxdmpadm settune command again to migrate the volume group onto DMP.

To verify the value of the dmp_native_support tunable, use the following command:

# vxdmpadm gettune dmp_native_support
         Tunable               Current Value  Default Value
----------------------------    ----------------    -----------------
dmp_native_support               on              off

 

Once tunable is set, scan disk again with vxdctl enable & see if you can see the disk

 

 

G

PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided.
 

sashi's picture

Hi ,

 Thanks for the reply.I tried with your steps but still the state of the disk is "error".

 It is a new setup not an upgraded one.

 

bash-3.2#  vxdmpadm gettune dmp_native_support
            Tunable               Current Value  Default Value
------------------------------    -------------  -------------
dmp_native_support                       on              off
bash-3.2#
 
============
 
bash-3.2# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
aluadisk0_0  auto:cdsdisk    -            -            online
aluadisk0_1  auto:cdsdisk    -            -            online
aluadisk0_2  auto:none       -            -            online invalid
aluadisk0_3  auto:LVM        -            -            LVM
aluadisk0_4  auto:LVM        -            -            LVM
hdiskdpd0    simple          -            -              error

after "vxdisk scandisks" the nodes in the /dev/vx/dmp , /dev/vx/rdmp disappears.

bash-3.2# ls -l /dev/vx/dmp
total 0
brw-------    1 root     system       50,  5 Dec 10 23:39 aluadisk0_0
brw-------    1 root     system       50, 11 Dec 10 23:39 aluadisk0_1
brw-------    1 root     system       50, 12 Dec 10 23:39 aluadisk0_2
brw-------    1 root     system       50,  8 Dec 10 23:39 aluadisk0_3
brw-------    1 root     system       50,  6 Dec 10 23:39 aluadisk0_4
brw-------    1 root     system       50,  9 Dec 10 23:39 aluadisk0_5
brw-------    1 root     system       50, 10 Dec 10 23:39 aluadisk0_6
brw-------    1 root     system       50,  4 Dec 10 23:39 aluadisk0_7
 
 
How to make persistent after the scandisks.? 
 
May i know when are these flags and error with the udid set?
 
bash-3.2# vxdisk list hdiskdpd0
Device:    hdiskdpd0
devicetag: hdiskdpd0
type:      simple
flags:     error private foreign
pubpaths:  block=/dev/hdiskdpd0 char=/dev/rhdiskdpd0
guid:      -
udid:      INVALID
site:      -
errno:     Device path not valid
 

 

 

sashi's picture

Hi ,

Could you please reply to the above query. Its important .Thank you

 

Gaurav Sangamnerkar's picture

Hello,

Are you able to see this device at OS layer ?

post the lspv output from the server, paste the exact command you have used to add foreign device , lastly paste the contents of /etc/vx/darecs file

 

G

PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided.
 

sashi's picture

Yes device is visible at OS level.

here is the output ;

 bash-3.2# lspv

hdisk0          00cdef2b6b36047f                    rootvg          active
hdisk1          00c676dc3f08af19                    rootvg          active
hdiskdpdctrl    none                                None
hdiskdpd0      none                                None
hdisk2          none                                None
hdisk14         none                                None
hdisk26         none                                None
hdisk38         none                                None
bash-3.2#
 
 
bash-3.2# vxddladm -f addforeign blockpath=/dev/hdiskdpd0 charpath=/dev/rhdiskdpd0
bash-3.2#
bash-3.2#
 
bash-3.2# cat /etc/vx/darecs
/dev/hdiskdpd0  foreign f       block   /dev/rhdiskdpd1 char
 
 
bash-3.2# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
hdisk0       auto:LVM        -            -            LVM
hdiskdpd0    simple          -            -            error
hdisk1       auto:LVM        -            -            LVM
 
 
bash-3.2# vxddladm listforeign all
 
The Paths included are
-----------------------
 
Based on Directory names:
-----------------------
 
Based on Full Path:
--------------------
/dev/hdiskdpd0         block  /dev/rhdiskdpd0          char  Suppress foreign
bash-3.2#
 
 
sashi's picture

 And we don't have the valid ASL .Added the disks as jbod.

after vxdctl enable and vxdisk scandisks the nodes in the /dev/vx/dmp and /dev/vx/rdmp disappears .

Is there any way to make them persistant..?

 

Gaurav Sangamnerkar's picture

Hi,

I am looking for options here, first I would like to see the disk in online state, then we can think of persistent device issues.

If the disk is visible from OS level, can you put a PV on it so that it has a PVID & then rescan the disks ?

 

G

PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided.
 

sashi's picture

Hi Gaurav,

  Here is the ouput ,disk has pvid but still after rescan and vxdctl enable disk is in error state

 

bash-3.2# lspv
hdisk0          00cdef2b6b36047f                    rootvg          active
hdisk1          00c676dc3f08af19                    rootvg          active
hdisk2          none                                None
hdisk3          none                                None
hdiskdpdctrl    none                                None
hdiskdpd0       000069fe000022e6                    testvg          active
hdisk13         none                                None
hdisk14         none                                None
hdisk23         none                                None
hdisk26         none                                None
hdisk33         none                                None
hdisk38         none                                None
 
 
bash-3.2# vxdisk scandisks
bash-3.2#
bash-3.2#
bash-3.2# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
hdisk0       auto:LVM        -            -            LVM
hdiskdpd0    simple          -            -            error
hdisk1       auto:LVM        -            -            LVM
hdisk2       auto            -            -            error
hdisk3       auto:none       -            -            online invalid
 

 

sashi's picture

 

Is there any changes we can make in ODM side..? I mean any attributes ?

sashi's picture

Hi,

Could you please provide any further suggestions..?

 

Gaurav Sangamnerkar's picture

Hi Sashi,

one thing, are you certain that this device is not supressed from vxvm's view, based on the outputs you gave

bash-3.2# vxddladm listforeign all
 
The Paths included are
-----------------------
 
Based on Directory names:
-----------------------
 
Based on Full Path:
--------------------
/dev/hdiskdpd0         block  /dev/rhdiskdpd0          char  Suppress foreign  <<<<<<<<<< is it supressed ???
bash-3.2#
 
Check from "vxdiskadm" menu if you can to & unsupress the device
 
you can also check if the device is excluded from vxvm's view
# vxddladm listexclude all
# vxdmpadm listexclude all
 
or any *.exclude files in /etc/vx directory ..
 
G

PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided.
 

sashi's picture

Hi,

No the disk is not excluded ,i didn't see any entry of the hdiskdpd in excluded files.Here is the ouput.

 

   bash-3.2# vxddladm listexclude all

 
The Diskarrays excluded
-----------------------
 
Based on Library names:
-----------------------
 
Based on VID, PID Combination:
------------------------------
 
==================
bash-3.2# vxdmpadm listexclude all
Devices excluded from VxVM:
--------------------------
 
Paths : None
 
Controllers : None
 
VID:PID : None
 
--------------------------
==========================
 
bash-3.2# cat /etc/vx/vxvm.exclude
exclude_all 0
paths
#
controllers
#
product
#
 
I tried to include the hdiskdpd but it is showing disk is not in excluded state.
 
"Device(s) currently not excluded"

 

sashi's picture

Hi,

Do you have any further suggestions? Disks are recognized by the OS and they are not in the exculded list also.Is therr any other way Vxvm can exclude the psuedo devices?Please suggest it is important.Thank you

 

Gaurav Sangamnerkar's picture

Hi, as this is urgent, I would suggest to open a technical support case to get an answer ...

What array you have in system ? I am not sure of Dynapath, is there a possiblity to supress that device from Dynapth & project device directly to DMP .. I am trying to troubleshoot the area of the problem

 

G

PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided.
 

sashi's picture
Hi Gaurav,
 
 
 Array type ATYPE: ALUA
 
Able to add the native devices to DMP when Dynapath is enabled.But when coming to this pseudo devices we are facing this issue.
Is there any other way DMP suppress the psuedo devices without the  valid ASL ? 
sashi's picture

Hi Gaurav,

Could you please reply for the above query.Thank you.

 

Gaurav Sangamnerkar's picture

Hi,

What is the setting for tpdmode ?

what is current setting for tpdmode native/pseudo ,set it to native & see

vxdmpadm setattr enclosure enclosure_name tpdmode=native

 

G

PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided.
 

sashi's picture

Hi Gaurav ,

Present setting for the tpdmode is "native".Unable to set the "pseudo" option for the enclosure=aluadisk0.

 

 

sashi's picture

Hi Gaurav,

Please clarify this doubt.
-In the list of devices we don't see the pseudo devices, and there is no enclosure corresponding to the pseudo devices.If the pseudo devices should have anything to do with the storage array ?

bash-3.2# vxddladm list devices
DEVICE               TARGET-ID    STATE   DDL-STATUS (ASL)
===============================================================
hdisk12              -            Online  CLAIMED (ALUA)
hdisk5               -            Online  CLAIMED (ALUA)
hdisk8               -            Online  CLAIMED (ALUA)
hdisk4               -            Online  CLAIMED (ALUA)
hdisk9               -            Online  CLAIMED (ALUA)
hdisk13              -            Online  CLAIMED (ALUA)
hdisk1               -            Online  CLAIMED (Disk)
hdisk0               -            Online  CLAIMED (Disk)
hdisk6               -            Online  CLAIMED (ALUA)
hdisk11              -            Online  CLAIMED (ALUA)
hdisk2               -            Online  CLAIMED (ALUA)
hdisk7               -            Online  CLAIMED (ALUA)
hdisk10              -            Online  CLAIMED (ALUA)
hdisk3               -            Online  CLAIMED (ALUA)
 
 
bash-3.2#  vxdmpadm listenclosure all
ENCLR_NAME        ENCLR_TYPE     ENCLR_SNO      STATUS       ARRAY_TYPE     LUN_COUNT
=======================================================================================
disk              Disk           DISKS                CONNECTED    Disk        2
aluadisk0         aluadisk       ALUAdisk             CONNECTED    ALUA        3
 
 
 

 

sashi's picture

HI Gaurav,

Could you please respond to the above query..? Thank you

sashi's picture

Hi,

Anyone in the group please respond to the above query.Thank you.

TonyGriffiths's picture

Hi

I do not recall Dynapath as a Third Party Multi-Pathing product that we have qualified in our HCL, have you any vendor documentation stating the support stance ?

What is the array/storage behind this ?

The error messages implies that the devices is not usable.

 

Cheers

tony

sashi's picture

Hi Tony,

Thanks for the reply.

The storage is Falconstor Ipstor.Dynapath is the he multipathing software for this storage and Dynapath uses a layer driver.

I didn't understand regarding the document .May i know what documentation you need exactly?

If the pseudo devices should have anything to do with the storage array ?

 

sashi's picture

Hi Tony,

Could you please respond for the query. Thank you

 "If the pseudo devices should have anything to do with the storage array ?"

 

TonyGriffiths's picture

Hi Sashi,

Regarding my Documentation query - Does the Array/Multi-path vendor provide any documentation on setting this up with Storage Foundation ?

We have not qualified that array/Multi-pathing solution with SF.

Here is the link to the Hardware Compatibility List

https://sort.symantec.com/hclcentral

 

cheers

tony

sashi's picture

Hi Tony,

 

  1) Does the Array/Multi-path vendor provide any documentation on setting this up with Storage Foundation?

 - No,we don't have the valid ASL added the disks as jbod.

 We are able to recognise the hdisk''s controlled by Dynapath we are not able to recognise the pusedo devices.

My Query is "If the pseudo devices should have anything to do with the storage array ?"

Thank you.