- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Changing Driectory Slow Response
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
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
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
тАО06-11-2009 05:51 PM
тАО06-11-2009 05:51 PM
Changing Driectory Slow Response
I am currently expriencing problems getting into a specific directory /dir1/dir2/dir3/dir4.
Its kind of weird since i can just go into any directory quickly but this specific directory when accessed seems to have hanged up my "cd" command.
What could be the problem? for almost 5 mins already my "cd /dir1/dir2/dir3/dir4" is still not finished.
TIA
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-11-2009 06:08 PM
тАО06-11-2009 06:08 PM
Re: Changing Driectory Slow Response
Either the disk is going to die or an NFS issue.
Check the latest contents of /var/adm/syslog/syslog.log
tail -20 /var/adm/syslog/syslog.log
Does it says about Disk problem or and NFS retry or inaccessible issue?
HTH,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-11-2009 06:20 PM
тАО06-11-2009 06:20 PM
Re: Changing Driectory Slow Response
Jun 12 05:46:51 CCB_SDS vmunix: SCSI: Read error -- dev: b 31 0x447100, errno: 126, resid: 1024,
Jun 12 05:46:51 CCB_SDS vmunix: blkno: 8, sectno: 16, offset: 8192, bcount: 1024.
Jun 12 05:46:51 CCB_SDS vmunix: SCSI: Read error -- dev: b 31 0x447000, errno: 126, resid: 1024,
Jun 12 05:46:52 CCB_SDS vmunix: LVM: VG 64 0x3f0000: Lost quorum.
Jun 12 05:46:51 CCB_SDS vmunix:
Jun 12 05:46:52 CCB_SDS above message repeats 7 times
Jun 12 05:46:52 CCB_SDS vmunix: This may block configuration changes and I/Os. In order to reestablish quorum at least 1 of the following PVs (represented by
current link) must become available:
Jun 12 05:46:52 CCB_SDS vmunix: <31 0x447000> <31 0x447100> <31 0x447200>
Jun 12 05:46:51 CCB_SDS vmunix: blkno: 8, sectno: 16, offset: 8192, bcount: 1024.
Jun 12 05:46:52 CCB_SDS vmunix: LVM: VG 64 0x3f0000: PVLink 31 0x447000 Failed! The PV is not accessible.
Jun 12 05:46:52 CCB_SDS vmunix: LVM: VG 64 0x3f0000: PVLink 31 0x447100 Failed! The PV is not accessible.
Jun 12 05:46:52 CCB_SDS vmunix: LVM: VG 64 0x3f0000: PVLink 31 0x447200 Failed! The PV is not accessible.
Jun 12 05:47:35 CCB_SDS vmunix: LVM: VG 64 0x3f0000: PVLink 31 0x447300 Failed! The PV is not accessible.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-11-2009 06:38 PM
тАО06-11-2009 06:38 PM
Re: Changing Driectory Slow Response
You've got Disk issues.
Do the following:
ls -l /dev/dsk |grep -E "7100|7000|7200|7300"
Check the pvdisplay status of these disks
These disks are surely not accessible as the message says above
Check the Controller status with ioscan.
Post more the output of these commands:
ls -l /dev/dsk |grep -E "7100|7000|7200|7300"
pvdisplay
vgdisplay output of the related disks.
Good Luck!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-11-2009 07:13 PM
тАО06-11-2009 07:13 PM
Re: Changing Driectory Slow Response
My VG can't be displayed!
root:/> vgdisplay -v /dev/vgebs01/
vgdisplay: Couldn't read the internal id of volume group "/dev/vgebs01/" from "/etc/lvmtab".
vgdisplay: Cannot display volume group "/dev/vgebs01/".
What should I do?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-11-2009 07:24 PM
тАО06-11-2009 07:24 PM
Re: Changing Driectory Slow Response
This is responsible for Volume Group error.
Please post the output of :
strings /etc/lvmtab
I'm afraid ioscan may hang here while querying for Physical Disks Status.
Can you post the status of ioscan -kfnC disk first and see if you can find the culprit disks also the Controller status associated with the disks.
This document should be referred for this situation:
http://docs.hp.com/en/5991-1236/When_Good_Disks_Go_Bad_WP.pdf
Good Luck!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-11-2009 08:02 PM
тАО06-11-2009 08:02 PM
Re: Changing Driectory Slow Response
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-11-2009 08:11 PM
тАО06-11-2009 08:11 PM
Re: Changing Driectory Slow Response
See the disk status: from error messages you should have 4 suspicious disks.
Also, Do you know if the system has hot-swap disk capability or not?
Check the machine model and OS ver.
Good Luck!!