- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Error in Syslog
Operating System - HP-UX
1748181
Members
4048
Online
108759
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
Discussions
Discussions
Forums
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
тАО04-29-2011 11:20 PM
тАО04-29-2011 11:20 PM
Dear Gurus,
Can anybody tell me the below error.
Apr 30 08:42:41 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 9: Some I/O requests to this LV are waiting
Apr 30 08:42:41 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 3: Some I/O requests to this LV are waiting
Apr 30 08:42:44 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 6: Some I/O requests to this LV are waiting
Apr 30 08:42:50 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 6: Some I/O requests to this LV are waiting
Apr 30 08:42:55 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 6: Some I/O requests to this LV are waiting
Apr 30 08:43:00 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 6: Some I/O requests to this LV are waiting
Apr 30 08:43:05 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 6: Some I/O requests to this LV are waiting
Apr 30 08:43:10 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 6: Some I/O requests to this LV are waiting
Apr 30 08:43:11 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 9: Some I/O requests to this LV are waiting
Apr 30 08:43:11 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 1: Some I/O requests to this LV are waiting
Apr 30 08:43:11 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 10: Some I/O requests to this LV are waiting
Apr 30 08:43:11 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 2: Some I/O requests to this LV are waiting
Apr 30 08:43:11 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 3: Some I/O requests to this LV are waiting
Apr 30 08:43:11 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 4: Some I/O requests to this LV are waiting
Apr 30 08:43:11 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 5: Some I/O requests to this LV are waiting
Apr 30 08:43:11 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 7: Some I/O requests to this LV are waiting
Apr 30 08:43:12 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 1: Some I/O requests to this LV are waiting
Apr 30 08:43:18 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 9: Some I/O requests to this LV are waiting
Apr 30 08:43:47 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 10: Some I/O requests to this LV are waiting
Apr 30 08:43:48 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 3: Some I/O requests to this LV are waiting
Apr 30 08:43:48 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 6: Some I/O requests to this LV are waiting
Apr 30 08:43:51 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 9: Some I/O requests to this LV are waiting
Apr 30 08:43:51 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 6: Some I/O requests to this LV are waiting
Apr 30 08:43:53 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 1: Some I/O requests to this LV are waiting
Apr 30 08:43:56 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 6: Some I/O requests to this LV are waiting
Apr 30 08:44:06 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 6: Some I/O requests to this LV are waiting
Apr 30 08:44:11 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 6: Some I/O requests to this LV are waiting
Apr 30 08:44:26 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 6: Some I/O requests to this LV are waiting
Thanks in Advance
Regards,
Ashis
Can anybody tell me the below error.
Apr 30 08:42:41 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 9: Some I/O requests to this LV are waiting
Apr 30 08:42:41 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 3: Some I/O requests to this LV are waiting
Apr 30 08:42:44 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 6: Some I/O requests to this LV are waiting
Apr 30 08:42:50 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 6: Some I/O requests to this LV are waiting
Apr 30 08:42:55 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 6: Some I/O requests to this LV are waiting
Apr 30 08:43:00 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 6: Some I/O requests to this LV are waiting
Apr 30 08:43:05 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 6: Some I/O requests to this LV are waiting
Apr 30 08:43:10 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 6: Some I/O requests to this LV are waiting
Apr 30 08:43:11 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 9: Some I/O requests to this LV are waiting
Apr 30 08:43:11 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 1: Some I/O requests to this LV are waiting
Apr 30 08:43:11 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 10: Some I/O requests to this LV are waiting
Apr 30 08:43:11 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 2: Some I/O requests to this LV are waiting
Apr 30 08:43:11 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 3: Some I/O requests to this LV are waiting
Apr 30 08:43:11 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 4: Some I/O requests to this LV are waiting
Apr 30 08:43:11 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 5: Some I/O requests to this LV are waiting
Apr 30 08:43:11 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 7: Some I/O requests to this LV are waiting
Apr 30 08:43:12 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 1: Some I/O requests to this LV are waiting
Apr 30 08:43:18 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 9: Some I/O requests to this LV are waiting
Apr 30 08:43:47 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 10: Some I/O requests to this LV are waiting
Apr 30 08:43:48 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 3: Some I/O requests to this LV are waiting
Apr 30 08:43:48 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 6: Some I/O requests to this LV are waiting
Apr 30 08:43:51 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 9: Some I/O requests to this LV are waiting
Apr 30 08:43:51 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 6: Some I/O requests to this LV are waiting
Apr 30 08:43:53 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 1: Some I/O requests to this LV are waiting
Apr 30 08:43:56 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 6: Some I/O requests to this LV are waiting
Apr 30 08:44:06 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 6: Some I/O requests to this LV are waiting
Apr 30 08:44:11 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 6: Some I/O requests to this LV are waiting
Apr 30 08:44:26 itdrd1ug vmunix: LVM: WARNING: VG 64 0x020000: LV 6: Some I/O requests to this LV are waiting
Thanks in Advance
Regards,
Ashis
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-29-2011 11:48 PM
тАО04-29-2011 11:48 PM
Solution
VG 64 0x020000 ==> look under /dev/vgXX the name of the VG corresponding to the "0x020000"
which has some issues .
Run vgdisplay -v vgXX to check the status of the lvol are they in available/sync state & PVs
are available.
Check any HW message is event.log
/var/opt/resmon/log/event.log
Do check with dd command the integrity of the internal disks.
Thanks
Manix
which has some issues .
Run vgdisplay -v vgXX to check the status of the lvol are they in available/sync state & PVs
are available.
Check any HW message is event.log
/var/opt/resmon/log/event.log
Do check with dd command the integrity of the internal disks.
Thanks
Manix
HP-UX been always lovable - Mani Kalra
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-30-2011 05:47 PM
тАО04-30-2011 05:47 PM
Re: Error in Syslog
Hi,
Are you getting these errors repeatedly in syslog or only once?
This could be also due to unavailability of LUNs from storage at time; which leads to larger time outs.
If you mwa (measureware agent) installed, then you can get the avwait time for luns in that time, which could describes the issue in brief.
Thanks,
Vivek
Are you getting these errors repeatedly in syslog or only once?
This could be also due to unavailability of LUNs from storage at time; which leads to larger time outs.
If you mwa (measureware agent) installed, then you can get the avwait time for luns in that time, which could describes the issue in brief.
Thanks,
Vivek
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-01-2011 02:36 AM
тАО05-01-2011 02:36 AM
Re: Error in Syslog
hi
check with ll /dev/*/group and look for minor no that corresponds to vg and check with vgdisplay -v vgname.
check for cur lv and open lv are same and check cur pv and act pv.
regards
MC
check with ll /dev/*/group and look for minor no that corresponds to vg and check with vgdisplay -v vgname.
check for cur lv and open lv are same and check cur pv and act pv.
regards
MC
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP