System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

Changing Driectory Slow Response

sysad_boy
Frequent Advisor

Changing Driectory Slow Response

Hi,

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
7 REPLIES
Nido
Trusted Contributor

Re: Changing Driectory Slow Response

Hi,

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,
" Let Villagers Be Happy!! "
sysad_boy
Frequent Advisor

Re: Changing Driectory Slow Response

Its not an NFS actually, but i saw something from the logs


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.


Nido
Trusted Contributor

Re: Changing Driectory Slow Response

Hi Again:

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!!


" Let Villagers Be Happy!! "
sysad_boy
Frequent Advisor

Re: Changing Driectory Slow Response

I think I already found an answer to my problem.

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?


Nido
Trusted Contributor

Re: Changing Driectory Slow Response

>>>>Jun 12 05:46:52 CCB_SDS vmunix: LVM: VG 64 0x3f0000: Lost quorum.

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!!
" Let Villagers Be Happy!! "
sysad_boy
Frequent Advisor

Re: Changing Driectory Slow Response

all disks are with CLAIMED status
Nido
Trusted Contributor

Re: Changing Driectory Slow Response

Did you try: ioscn -fnC disk
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!!
" Let Villagers Be Happy!! "