- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- How to interpret HP-UX device numbers from errors ...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
09-08-2011 02:28 AM
09-08-2011 02:28 AM
Hi all
I have a system running 11.31 in which it uses as its storage the NetApp. I have the following when using dmesg and in syslog
cat /var/adm/syslog/syslog.log | grep -i warning
Sep 2 19:06:59 prep01 vmunix: DIAGNOSTIC SYSTEM WARNING:
Sep 4 20:07:52 prep01 vmunix: LVM: WARNING: VG 64 0x010000: LV 1: Some I/O requests to this LV are waiting
Sep 4 20:07:53 prep01 vmunix: LVM: WARNING: VG 64 0x020000: LV 2: Some I/O requests to this LV are waiting
Sep 4 20:07:53 prep01 vmunix: LVM: WARNING: VG 64 0x010000: LV 2: Some I/O requests to this LV are waiting
Sep 7 13:41:54 prep01 vmunix: LVM: WARNING: VG 64 0x010000: LV 2: Some I/O requests to this LV are waiting
Sep 7 18:37:53 prep01 vmunix: LVM: WARNING: VG 64 0x010000: LV 2: Some I/O requests to this LV are waiting
dmesg:
Sep 8 11:30
...
300)
IO details : blkno : 10088237, sector no : 20176474
class : lunpath, instance 9
Asynchronous write failed on LUN (dev=0x1f040300)
IO details : blkno : 10088269, sector no : 20176538
class : lunpath, instance 12
Asynchronous write failed on LUN (dev=0x1f040200)
IO details : blkno : 22878962, sector no : 45757924
class : lunpath, instance 12
Asynchronous write failed on LUN (dev=0x1f040200)
IO details : blkno : 92739631, sector no : 185479262
class : lunpath, instance 13
Asynchronous write failed on LUN (dev=0x1f040300)
IO details : blkno : 10088373, sector no : 20176746
DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility is no longer receiving excessive
errors from the I/O subsystem. 53 I/O error entries were lost.
class : lunpath, instance 12
Asynchronous write failed on LUN (dev=0x1f040200)
IO details : blkno : 83687711, sector no : 167375422
Standard input
So How can I decode the LUN (dev=0x1f040300) and 0x010000?
regards
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-08-2011 03:45 AM
09-08-2011 03:45 AM
SolutionHi,
VG 64 0x010000: LV 1 means: VG (version 1 ) with major number 01 and logical volume 1, you can get it with the following command
# ll /dev/*/group
To get the LUN name of dev=0x1f040300
# ll /dev/*dsk | grep 040300
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-08-2011 05:02 AM
09-08-2011 05:02 AM
Re: How to interpret HP-UX device numbers from errors in syslog
Hi
Thanks a lot, did work fine, so I have to grep for the last 6 digits right?
Any idea what could be causing this Asynchronous write fails? or the "Some I/O requests to this LV are waiting" message?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-08-2011 05:09 AM
09-08-2011 05:09 AM
Re: How to interpret HP-UX device numbers from errors in syslog
These errors means your write operations are not successfully finished, you should check disk subsytem for any errors.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-08-2011 01:56 PM
09-08-2011 01:56 PM
Re: How to interpret HP-UX device numbers from errors in syslog
http://ktkb.wordpress.com/2011/01/13/decoding-device-names-from-vmunix-errors-in-syslog/
This was written more for 11.11 and 11.23, but should apply to 11.31, too.
Kris Knigga