vmunix: function == 0x2483DEA0, arg == 0x80A9C800, ticks == 0xFBD25FDE, flags == 0x0

Getting following error message in /var/adm/syslog/error.log

ar 30 15:11:59 anlbilph vmunix: function == 0x2483DEA0, arg == 0x80A9C800, ticks == 0xFBD25FDE,  flags == 0x0
Mar 30 15:11:59 anlbilph vmunix: function == 0x2483DEA0, arg == 0x80A9C800, ticks == 0xFBD25FDD,  flags == 0x0
Mar 30 15:11:59 anlbilph vmunix: function == 0x2483DEA0, arg == 0x80A9C800, ticks == 0xFBD25FDC,  flags == 0x0
Mar 30 15:11:59 anlbilph vmunix: function == 0x2483DEA0, arg == 0x80A9C800, ticks == 0xFBD25FDB,  flags == 0x0
Mar 30 15:11:59 anlbilph vmunix: function == 0x2483DEA0, arg == 0x80A9C800, ticks == 0xFBD25FDA,  flags == 0x0
Mar 30 15:11:59 anlbilph vmunix: function == 0x2483DEA0, arg == 0x80A9C800, ticks == 0xFBD25FD9,  flags == 0x0
Mar 30 15:11:59 anlbilph vmunix: function == 0x2483DEA0, arg == 0x80A9C800, ticks == 0xFBD25FD8,  flags == 0x0
Mar 30 15:11:59 anlbilph vmunix: function == 0x2483DEA0, arg == 0x80A9C800, ticks == 0xFBD25FD7,  flags == 0x0
Mar 30 15:11:59 anlbilph vmunix: function == 0x2483DEA0, arg == 0x80A9C800, ticks == 0xFBD25FD6,  flags == 0x0
Mar 30 15:11:59 anlbilph vmunix: function == 0x2483DEA0, arg == 0x80A9C800, ticks == 0xFBD25FD5,  flags == 0x0
Mar 30 15:11:59 anlbilph vmunix: function == 0x2483DEA0, arg == 0x80A9C800, ticks == 0xFBD25FD4,  flags == 0x0
Mar 30 15:11:59 anlbilph vmunix: function == 0x2483DEA0, arg == 0x80A9C800, ticks == 0xFBD25FD3,  flags == 0x0
Mar 30 15:11:59 anlbilph vmunix: function == 0x2483DEA0, arg == 0x80A9C800, ticks == 0xFBD25FD2,  flags == 0x0
Mar 30 15:11:59 anlbilph vmunix: function == 0x2483DEA0, arg == 0x80A9C800, ticks == 0xFBD25FD1,  flags == 0x0
Mar 30 15:11:59 anlbilph vmunix: function == 0x2483DEA0, arg == 0x80A9C800, ticks == 0xFBD25FD0,  flags == 0x0

# echo "0x2483DEA0/i" |adb /stand/vmunix /dev/kmem
mpt_os_callback:
mpt_os_callback:                STD             r2,-16(r30)

Please raise a case with HP, In your system, mpt drivers needs to be updated.

New LUN assigned to HP-Unix 11iv3 was in NO_HW status:

New LUN assigned to HP-Unix 11iv3 was in NO_HW status:

In dmesg following error messages was coming;

class : lunpath, instance 59
Evpd inquiry page 83h/80h failed or the current page 83h/80h data do not match the previous known page 83h/80h data on LUN id 0x0 probed beneath the target path (class = tgtpath, instance = 8) The lun path is (class = lunpath, instance 59).Run 'scsimgr replace_wwid' command to validate the change

class : lunpath, instance 58
Evpd inquiry page 83h/80h failed or the current page 83h/80h data do not match the previous known page 83h/80h data on LUN id 0x0 probed beneath the target path (class = tgtpath, instance = 7) The lun path is (class = lunpath, instance 58).Run 'scsimgr replace_wwid' command to validate the change

#check the lunpath number which is seens in the output it may be blocking the disk visisblity:

please run below command :
#scsimgr replace
scsimgr -f replace_wwid -C lunpath -I   ??? <whatt you see in dmesg>


scsimgr replace_wwid -C lunpath -I 58
scsimgr replace_wwid -C lunpath -I 59


#insf
#ioscan -fnC disk   
#dmesg

Changing the disk-naming scheme

You can either use enclosure-based naming for disks or the operating system’s naming scheme. VxVM commands display device names according the current naming scheme.
The default naming scheme is enclosure-based naming (EBN). When you install or upgrade a Storage Foundation product, the naming scheme is set to enclosure-based naming, with the following exception. If you explicitly set the naming scheme for an existing installation to operating system-based naming, the setting is preserved when you upgrade. That is, if you used the vxddladm set namingscheme=osn command for the existing installation, the upgraded 5.1 product retains the operating system-based naming.

To change the disk-naming scheme

Select Change the disk naming scheme from the vxdiskadm main menu to change the disk-naming scheme that you want VxVM to use. When prompted, enter y to change the naming scheme.
Alternatively, you can change the naming scheme from the command line. Use the following command to select enclosure-based naming:

# vxddladm set namingscheme=ebn [persistence={yes|no}] \

[use_avid=yes|no] [lowercase=yes|no]
Use the following command to select operating system-based naming:

# vxddladm set namingscheme=osn [persistence={yes|no}] \

[lowercase=yes|no]
The optional persistence argument allows you to select whether the names of disk devices that are displayed by VxVM remain unchanged after disk hardware has been reconfigured and the system rebooted. By default, enclosure-based naming is persistent. Operating system-based naming is not persistent by default.

By default, the names of the enclosure are converted to lowercase, regardless of the case of the name specified by the ASL. The enclosure-based device names are therefore in lower case. Set the lowercase=no option to suppress the conversion to lowercase.

For enclosure-based naming, the use_avid option specifies whether the Array Volume ID is used for the index number in the device name. By default, use_avid=yes, indicating the devices are named as enclosure_avid. If use_avid is set to no, DMP devices are named as enclosure_index. The index number is assigned after the devices are sorted by LUN serial number.
The change is immediate whichever method you use.

When you try to shrink Volume/File system using '-' sign in the command as follows, it results in an error..

When you try to shrink Volume/File system using '-' sign in the command as follows, it results in an error..

#/etc/vx/bin/vxresize -g DG Volume_Name -Size E.g. #/etc/vx/bin/vxresize -g testdg testvol -2g #/etc/vx/bin/vxresize -g testdg testvol -2g vxresize: invalid option -- 2 VxVM vxresize INFO V-5-1-10092 usage: vxresize [-hHvMDxsnbf] [-F fstype] [-g diskgroup] [-t tag] [-o verify|override] volume length [media...]

Since '-2g' starts with '-' character, the standard UNIX getopt will treat it as an option.

Resolution:

In order to tell getopt(3) to terminate the option scanning, you have to specify '--'.

#/etc/vx/bin/vxresize -g DG Volume_Name -- -Size E.g. #/etc/vx/bin/vxresize -g testdg testvol -- -2g