HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: HP VM integrity problem: Rejecting an i/o requ...
Operating System - HP-UX
1836188
Members
2461
Online
110096
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-18-2007 12:22 AM
05-18-2007 12:22 AM
HP VM integrity problem: Rejecting an i/o request to a closed LVOL
Hello,
I have of an rx8640 that I installed on HP integrity VM on a partition.
VMhost + 2 VM guests
Virtual Machine Name VM # OS Type State #VCPUs #Devs #Nets Memory Runsysid
==================== ===== ======= ========= ====== ===== ===== ======= ========
vmercury 2 HPUX Off 1 1 2 1300 MB 0
vuranus 6 HPUX On (OS) 1 2 2 2 GB 0
vmercury
#####################
Guest mercury with no problems
#####################
# hpvmstatus -Pvmercury -v
Version A.02.00.00
[Virtual Machine Details]
Virtual Machine Name VM # OS Type State
==================== ===== ======= ========
vmercury 2 HPUX Off
[Authorized Administrators]
Oper Groups:
Admin Groups:
Oper Users:
Admin Users:
[Virtual CPU Details]
vCPUs Type Entitlement Maximum
====== ======= =========== =======
1 10.0% 100.0%
[Memory Details]
Total Reserved
Memory Memory
=========== ===========
1300 MB 64 MB
[Storage Interface Details]
Guest Physical
Device Adaptor Bus Dev Ftn Tgt Lun Storage Device
======= ========== === === === === === ========= =========================
disk scsi 0 2 0 0 0 lv /dev/vgmercury/rlvmercury
[Network Interface Details]
Interface Adaptor Name/Num PortNum Bus Dev Ftn Mac Address
========= ========== ========== ======= === === === =================
vswitch lan localnet 1 0 0 0 42-bb-b1-ea-e6-3f
vswitch lan clan1 2 0 1 0 de-72-9b-8e-18-1c
[Misc Interface Details]
Guest Physical
Device Adaptor Bus Dev Ftn Tgt Lun Storage Device
======= ========== === === === === === ========= =========================
serial com1 tty console
now a second guest that have an additional space lvolume of 200GB on SAN, below is the status:
# hpvmstatus -Pvuranus -v
Version A.02.00.00
[Virtual Machine Details]
Virtual Machine Name VM # OS Type State
==================== ===== ======= ========
vuranus 6 HPUX On (OS)
[Authorized Administrators]
Oper Groups:
Admin Groups:
Oper Users:
Admin Users:
[Virtual CPU Details]
vCPUs Type Entitlement Maximum
====== ======= =========== =======
1 10.0% 100.0%
[Memory Details]
Total Reserved
Memory Memory
=========== ===========
2 GB 64 MB
[Storage Interface Details]
Guest Physical
Device Adaptor Bus Dev Ftn Tgt Lun Storage Device
======= ========== === === === === === ========= =========================
disk scsi 0 0 0 0 0 lv /dev/vgsuranus/rlvsuranus
disk scsi 0 0 0 2 0 lv /dev/vgdura/rlvdura
[Network Interface Details]
Interface Adaptor Name/Num PortNum Bus Dev Ftn Mac Address
========= ========== ========== ======= === === === =================
vswitch lan clan1 1 0 1 0 5e-f3-38-ee-9e-39
vswitch lan localnet 2 0 2 0 56-27-42-c1-4f-43
[Misc Interface Details]
Guest Physical
Device Adaptor Bus Dev Ftn Tgt Lun Storage Device
======= ========== === === === === === ========= =========================
serial com1 tty console
we are having an I/O error problem on VM host (bdf command) after installing + rebooting the second guest.
# bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 1540096 321640 1208944 21% /
/dev/vg00/lvol1 1009705 190259 718475 21% /stand
/dev/vg00/lvol8 6144000 1735976 4374760 28% /var
/dev/vg00/lvol7 6668288 2508680 4127120 38% /usr
bdf: /uranus: I/O error
/dev/vg00/lvol6 3588096 179528 3382008 5% /tmp
bdf: /suranus: I/O error
/dev/vg00/lvol5 6668288 3309968 3332136 50% /opt
/dev/vg00/lvol4 5128192 16808 5071464 0% /home
# cat /etc/fstab
/dev/vg00/lvol3 / vxfs delaylog 0 1
/dev/vg00/lvol1 /stand hfs defaults 0 1
/dev/vg00/lvol4 /home vxfs delaylog 0 2
/dev/vg00/lvol5 /opt vxfs delaylog 0 2
/dev/vg00/lvol6 /tmp vxfs delaylog 0 2
/dev/vg00/lvol7 /usr vxfs delaylog 0 2
/dev/vg00/lvol8 /var vxfs delaylog 0 2
/dev/vgmercury/lvmercury /mercury vxfs rw,suid,largefiles,delaylog,datainlog 0 2
/dev/vgsuranus/lvsuranus /suranus vxfs rw,suid,largefiles,delaylog,datainlog 0 2
/dev/vgdura/lvdura /uranus vxfs rw,suid,largefiles,delaylog,datainlog 0 2
Note:
system disks of the two VM guests are on SAN
data disk of 200GB of second Vm guest is on SAN also.
the VM host system is running on an internal disk.
after rebooting the VM host (after having this error) , the second guest's disk data disappeared.
#############################
the error found in the logs
#############################
May 18 14:02:03 saturne hpvmapp vuranus[5094]: VM Restart
May 18 14:25:13 saturne hpvmapp vuranus[6259]: VM Restart
May 18 14:34:55 saturne vmunix: LVM: Rejecting an i/o request to a closed LVOL.
May 18 14:34:55 saturne vmunix: msgcnt 1 vxfs: mesg 025: vx_wsuper - /dev/vgdura/lvdura file system super-block update failed
May 18 14:34:55 saturne vmunix: msgcnt 2 vxfs: mesg 031: vx_disable - /dev/vgdura/lvdura file system disabled
May 18 14:34:56 saturne vmunix: msgcnt 3 vxfs: mesg 025: vx_wsuper - /dev/vgsuranus/lvsuranus file system super-block update failed
May 18 14:34:56 saturne vmunix: msgcnt 4 vxfs: mesg 031: vx_disable - /dev/vgsuranus/lvsuranus file system disabled
please advise.
Regards.
I have of an rx8640 that I installed on HP integrity VM on a partition.
VMhost + 2 VM guests
Virtual Machine Name VM # OS Type State #VCPUs #Devs #Nets Memory Runsysid
==================== ===== ======= ========= ====== ===== ===== ======= ========
vmercury 2 HPUX Off 1 1 2 1300 MB 0
vuranus 6 HPUX On (OS) 1 2 2 2 GB 0
vmercury
#####################
Guest mercury with no problems
#####################
# hpvmstatus -Pvmercury -v
Version A.02.00.00
[Virtual Machine Details]
Virtual Machine Name VM # OS Type State
==================== ===== ======= ========
vmercury 2 HPUX Off
[Authorized Administrators]
Oper Groups:
Admin Groups:
Oper Users:
Admin Users:
[Virtual CPU Details]
vCPUs Type Entitlement Maximum
====== ======= =========== =======
1 10.0% 100.0%
[Memory Details]
Total Reserved
Memory Memory
=========== ===========
1300 MB 64 MB
[Storage Interface Details]
Guest Physical
Device Adaptor Bus Dev Ftn Tgt Lun Storage Device
======= ========== === === === === === ========= =========================
disk scsi 0 2 0 0 0 lv /dev/vgmercury/rlvmercury
[Network Interface Details]
Interface Adaptor Name/Num PortNum Bus Dev Ftn Mac Address
========= ========== ========== ======= === === === =================
vswitch lan localnet 1 0 0 0 42-bb-b1-ea-e6-3f
vswitch lan clan1 2 0 1 0 de-72-9b-8e-18-1c
[Misc Interface Details]
Guest Physical
Device Adaptor Bus Dev Ftn Tgt Lun Storage Device
======= ========== === === === === === ========= =========================
serial com1 tty console
now a second guest that have an additional space lvolume of 200GB on SAN, below is the status:
# hpvmstatus -Pvuranus -v
Version A.02.00.00
[Virtual Machine Details]
Virtual Machine Name VM # OS Type State
==================== ===== ======= ========
vuranus 6 HPUX On (OS)
[Authorized Administrators]
Oper Groups:
Admin Groups:
Oper Users:
Admin Users:
[Virtual CPU Details]
vCPUs Type Entitlement Maximum
====== ======= =========== =======
1 10.0% 100.0%
[Memory Details]
Total Reserved
Memory Memory
=========== ===========
2 GB 64 MB
[Storage Interface Details]
Guest Physical
Device Adaptor Bus Dev Ftn Tgt Lun Storage Device
======= ========== === === === === === ========= =========================
disk scsi 0 0 0 0 0 lv /dev/vgsuranus/rlvsuranus
disk scsi 0 0 0 2 0 lv /dev/vgdura/rlvdura
[Network Interface Details]
Interface Adaptor Name/Num PortNum Bus Dev Ftn Mac Address
========= ========== ========== ======= === === === =================
vswitch lan clan1 1 0 1 0 5e-f3-38-ee-9e-39
vswitch lan localnet 2 0 2 0 56-27-42-c1-4f-43
[Misc Interface Details]
Guest Physical
Device Adaptor Bus Dev Ftn Tgt Lun Storage Device
======= ========== === === === === === ========= =========================
serial com1 tty console
we are having an I/O error problem on VM host (bdf command) after installing + rebooting the second guest.
# bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 1540096 321640 1208944 21% /
/dev/vg00/lvol1 1009705 190259 718475 21% /stand
/dev/vg00/lvol8 6144000 1735976 4374760 28% /var
/dev/vg00/lvol7 6668288 2508680 4127120 38% /usr
bdf: /uranus: I/O error
/dev/vg00/lvol6 3588096 179528 3382008 5% /tmp
bdf: /suranus: I/O error
/dev/vg00/lvol5 6668288 3309968 3332136 50% /opt
/dev/vg00/lvol4 5128192 16808 5071464 0% /home
# cat /etc/fstab
/dev/vg00/lvol3 / vxfs delaylog 0 1
/dev/vg00/lvol1 /stand hfs defaults 0 1
/dev/vg00/lvol4 /home vxfs delaylog 0 2
/dev/vg00/lvol5 /opt vxfs delaylog 0 2
/dev/vg00/lvol6 /tmp vxfs delaylog 0 2
/dev/vg00/lvol7 /usr vxfs delaylog 0 2
/dev/vg00/lvol8 /var vxfs delaylog 0 2
/dev/vgmercury/lvmercury /mercury vxfs rw,suid,largefiles,delaylog,datainlog 0 2
/dev/vgsuranus/lvsuranus /suranus vxfs rw,suid,largefiles,delaylog,datainlog 0 2
/dev/vgdura/lvdura /uranus vxfs rw,suid,largefiles,delaylog,datainlog 0 2
Note:
system disks of the two VM guests are on SAN
data disk of 200GB of second Vm guest is on SAN also.
the VM host system is running on an internal disk.
after rebooting the VM host (after having this error) , the second guest's disk data disappeared.
#############################
the error found in the logs
#############################
May 18 14:02:03 saturne hpvmapp vuranus[5094]: VM Restart
May 18 14:25:13 saturne hpvmapp vuranus[6259]: VM Restart
May 18 14:34:55 saturne vmunix: LVM: Rejecting an i/o request to a closed LVOL.
May 18 14:34:55 saturne vmunix: msgcnt 1 vxfs: mesg 025: vx_wsuper - /dev/vgdura/lvdura file system super-block update failed
May 18 14:34:55 saturne vmunix: msgcnt 2 vxfs: mesg 031: vx_disable - /dev/vgdura/lvdura file system disabled
May 18 14:34:56 saturne vmunix: msgcnt 3 vxfs: mesg 025: vx_wsuper - /dev/vgsuranus/lvsuranus file system super-block update failed
May 18 14:34:56 saturne vmunix: msgcnt 4 vxfs: mesg 031: vx_disable - /dev/vgsuranus/lvsuranus file system disabled
please advise.
Regards.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-18-2007 04:46 AM
05-18-2007 04:46 AM
Re: HP VM integrity problem: Rejecting an i/o request to a closed LVOL
Hi,
VM guests use one of 3 things as a backing store:
1. a physical disk (/dev/rdsk/...)
2. a volume (LVM or VxVM)
3. a file in a filesystem (/myVMs/VM1/vm1.dsk )
In all cases these entities are presented to the VM guest as a physical disk.
It looks to me like on the VM host you are trying to mount the backing store for the VM guest as a filesystem - you can't do that! It's not a filesystem. Don't try and mount backing stores on your VM host as filesystems.
HTH
Duncan
I am an HPE Employee
VM guests use one of 3 things as a backing store:
1. a physical disk (/dev/rdsk/...)
2. a volume (LVM or VxVM)
3. a file in a filesystem (/myVMs/VM1/vm1.dsk )
In all cases these entities are presented to the VM guest as a physical disk.
It looks to me like on the VM host you are trying to mount the backing store for the VM guest as a filesystem - you can't do that! It's not a filesystem. Don't try and mount backing stores on your VM host as filesystems.
HTH
Duncan
I am an HPE Employee

The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP