Simpler Navigation for Servers and Operating Systems
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
Operating System - Tru64 Unix
cancel
Showing results for 
Search instead for 
Did you mean: 

ls and process problem

jack wu_2
Occasional Advisor

ls and process problem

I can't list the directory.
showfile exp is normal.
but ls exp, the system will hang.Ctrl^C no response.
There are a lot of Uninterruptible sleeping process, and can't kill it. but I can't reboot system.
What i can do?
thanks
jack

#showfile exp
Id Vol PgSz Pages XtntType Segs SegSz I/O Perf File
4a3.8013 1 16 1 simple ** ** ftx 100% exp
#ls exp

other terminal
13529 ttyp2 U + 0:00.00 ls exp
26266 ?? U 0:00.00 rm -rf exp
26439 ?? U 0:00.01 fuser -cu exp


11 REPLIES
Ralf Puchner
Honored Contributor

Re: ls and process problem

maybe an I/O or resource problem. Any informations within binary.errlog or messages?
Help() { FirstReadManual(urgently); Go_to_it;; }
Joris Denayer
Respected Contributor

Re: ls and process problem

Jack,

Is there a relation between this problem and your previous question about "interpreting collect data of a poor performing system"

Joris
To err is human, but to really faul things up requires a computer
Hein van den Heuvel
Honored Contributor

Re: ls and process problem


You wouldn't happen to be dealing with an NFS mounted directory, or have an NFS mount poitn in your path? If you do, there might be a networkign problem. Maybe try tcp instead of udp? try soft mount versus hard?

Hein.
jack wu_2
Occasional Advisor

Re: ls and process problem

Hi all
Joris this is two problem on two alpha server, there isn't relation between "collect" and "ls".

The corrupt directory isn't NFS,
If we fork many processes to modify one file, then the process will be hang and can't be killed. but I don't know the reason of the directory will be corrupt.

The sys_check -config file is attached.

thanks
jack
Joris Denayer
Respected Contributor

Re: ls and process problem

In atachment, the trace command.

Install it on your system
and run

# trace -o /tmp/ls_trace.txt -T ls exp

kill the process from another session.
In the file /tmp/ls_trace.txt, you should now be able to see where the ls command is hanging.

Good Luck
To err is human, but to really faul things up requires a computer
Joris Denayer
Respected Contributor

Re: ls and process problem

In my previous reply, i wrote:

Kill the process. Obviously, this must be
Kill the ls-process

Rgrds
To err is human, but to really faul things up requires a computer
Ralf Puchner
Honored Contributor

Re: ls and process problem

why not opening a call within a support center for a detailed analyze?
Help() { FirstReadManual(urgently); Go_to_it;; }
Michael Schulte zur Sur
Honored Contributor

Re: ls and process problem

Hi Jack,

can you give us the complete path to exp?

greetings,

Michael
Michael Schulte zur Sur
Honored Contributor

Re: ls and process problem

Hi,

can you check on that?

greetings,

Michael

Operational: chvol failing on one or more advfs domains.
This is typically caused by incorrect links in /etc/fdmns/.../... . Investigate and correct.

chvol /dev/vol/rootdg/rootvol root_domain Failed
chvol /dev/vol/rootdg/vol-rz0g usr_domain Failed
chvol /dev/vol/rootdg/vol-rz0h var_domain Failed

Michael Schulte zur Sur
Honored Contributor

Re: ls and process problem

Hi Jack,

could you solve the problem?

Michael
jack wu_2
Occasional Advisor

Re: ls and process problem

Hi Michael
I called HP support, he suggest me use dbx to trace the lock process, maybe a process cause it. Because the system can't force crash to analyze core dump, so that the case is hang up. The root cause isn't found.

thanks
jack