ls command hangs in certain directories
Alex Duffy
certain directories. If I change to the logging directory of one of the
hung applications and do an ls it will hang like this from ps. Not it
consumes no time.
standard 77714 75872 0 18:51:58 pts/7 0:00 /usr/bin/ls -F
The kill -15 or -9 do not kill it.
Reboot the machine and its OK. Its always the same specific directorys
which have this problem.
What I am trying to do is find out what the bug is that causes my
application to hang and this is something that I see at the same time.
Can any one suggest how to find out what ls has tried to access that is
locked ?
How to see what resource could be locked ?
A strange thing is that an attach with dbx fails.
$ dbx -a77714
Waiting to attach to process 77714 ...
Never gets to attach.
But running LS within dbx works, like this.
$ dbx /usr/bin/ls
Type 'help' for help.
reading symbolic information ...warning: no source compiled with -g
(dbx) where
__start() at 0x10000100
(dbx) next
stopped in . at 0x10000104
0x10000104 (???) 7c6e1b78 mr r14,r3
(dbx) c
PIPESPlatform.socket pipes.log
execution completed
(dbx) c
cannot continue execution
(dbx) where
_exit() at 0xd001b140
exit(??) at 0xd0014254
main(??, ??) at 0x10002544
(dbx)
Does anyone have a suggestion on how I might debug this or what could be
locked ?
Thanks
Alex
--
FICS Group.
Phone +32 2 714.43.21 GSM +32 (0) 495 20.11.72
LAIX Software Consulting
inaccessable at the time you tried this test?
Regards,
Paul
Helmut Leininger
Another guess: corrupted file system. I once came across a similar problem
(hanging ls). The reason was that the "." entry had disappeared. Unmount the
file system and try fsck.
Regards
--
Helmut Leininger
Bull AG / Vienna
Open Systems Support
Email: h.lei...@bull.at
helmut.l...@bull.net
This opinion is mine and not necessarily that of my employer.
No guarantees whatsoever.
rob
> The ls command just hangs when my application has hung. Its only in
Situations :
1) nfs mount where the nfs server is slow
2) lotsa files in the directory, use 'find . -ls' instead
3) filesystem problems
4) very dynamic directory
5) combinations of 1,2,3,4
Alex Duffy
a sub directory of the mount point from a very fast sun box. The directory
that I am asking about is interesting because it is local.
Thanks
for your suggestion.
Alex
Alex Duffy
system every few hours. I will keep experimenting to find a cause.
Thanks
Alex
Nicholas Dronen wrote:
> I'm more inclined to believe that this is a bug -- and such bugs
> do exist. I've experienced the same thing on a local filesystem
> on an SSA array. I've also experienced it on an automounted filesystem.
> The problem is that for some reason, stat(2) on a file in that directory
> simply doesn't return. In both of the above cases, there has been *no*
> problem doing and ls -l or and ls -F in the subdirectories of the filesystem --
> they would only hang unkillably in the mount point of the filesystem.
>
> Anyway, someone who's sufficiently clued to use dbx on the process
> would probably notice whether the filesytem was nfs-mounted.
>
> It's a bug.
Alex Duffy
Rob Kouwenberg wrote:
> Alex Duffy <a...@ficsgrp.com> wrote:
>
> > The ls command just hangs when my application has hung. Its only in
>
> Situations :
> 1) nfs mount where the nfs server is slow
its not, is multi processor and almost unused.
>
> 2) lotsa files in the directory, use 'find . -ls' instead
3-4 files
>
> 3) filesystem problems
possible
>
> 4) very dynamic directory
? could be. Do you know an efficient way to monitor the activity of a
directory? The only problem is that the processors are 95% idle.
>
> 5) combinations of 1,2,3,4
Many Thanks
Alex
John Jaszczak
If you do a "df" on another session when the "ls" hangs, can you see the
cross-mounted filesystem or does the "df" also hang?
-JAZZ
--
John Jaszczak
Romac International
Assigned to: Harmonic Systems, Inc.
jjas...@harmonic.com
612-321-4139
Alex Duffy wrote in message <37E5F932...@ficsgrp.com>...
Todd Sands (Frankendata)
The directory itself doesn't have to be nfs mounted, if you have a
directory in the $PATH ahead of it it cause the same problem.
T
Alex Duffy (a...@ficsgrp.com) wrote:
: It is not NFS mounted but it happens in one NFS mounted directory as well. Its
:
rob
> Rob Kouwenberg wrote:
> its not, is multi processor and almost unused.
> 3-4 files
> >
> > 3) filesystem problems
> possible
> > 4) very dynamic directory
> ? could be. Do you know an efficient way to monitor the activity of a
> directory? The only problem is that the processors are 95% idle.
> > 5) combinations of 1,2,3,4
Hmm round two.
Let me gues your situation :
AIX 421 with bos.rte.filesystems lower than 4.2.1.7
If so : known bug, update bos.rte.filesystems