Core dump in / when "ls -lt" under Solaris 10 (10/08)
underh20.s...@gmail.com
I just installed the latest version of Solaris 10 (10/08) to our
server. The system booted up ok and I can log on with no issue.
However, when we try to issue "ls -lt" command at the / directory, we
are not getting any output and the prompt just hanged there. This is
very strange since we can do the same "ls -lt" command at any other
directories and get the result.
Another strange thing is that the "core" dump file is created anytime
we issue the "ls -lt" command in the / directory. Why ? I tried to
fsck the entire root disk but to no avail.
Anyone knows how to resolve this ? Thanks, Bill.
# cd /
# ls -lt
< just hanged there !!!>
^C#
# ls -lt core
$ ls -lt /core
-rw------- 1 root root 4452190 Mar 4 19:03 /core
Ewald Ertl
On 5 Mrz., 01:11, underh20.scubadiv...@gmail.com wrote:
> Hello everyone,
>
> I just installed the latest version of Solaris 10 (10/08) to our
> server. The system booted up ok and I can log on with no issue.
> However, when we try to issue "ls -lt" command at the / directory, we
> are not getting any output and the prompt just hanged there. This is
> very strange since we can do the same "ls -lt" command at any other
> directories and get the result.
>
> Another strange thing is that the "core" dump file is created anytime
> we issue the "ls -lt" command in the / directory. Why ? I tried to
> fsck the entire root disk but to no avail.
>
> Anyone knows how to resolve this ? Thanks, Bill.
ls without any option works?
Have you tried to investigate the problem with truss?
>
> # cd /
> # ls -lt
>
> < just hanged there !!!>
>
> ^C#
>
> # ls -lt core
> $ ls -lt /core
> -rw------- 1 root root 4452190 Mar 4 19:03 /core
file core - reveals which process created the core dump.
pstack core - show you the stack strace of the core
HTH
Ewald
Stefaan A Eeckels
underh20.s...@gmail.com wrote:
> However, when we try to issue "ls -lt" command at the / directory, we
> are not getting any output and the prompt just hanged there. This is
> very strange since we can do the same "ls -lt" command at any other
> directories and get the result.
>
> Another strange thing is that the "core" dump file is created anytime
> we issue the "ls -lt" command in the / directory. Why ? I tried to
> fsck the entire root disk but to no avail.
What does
# cd /
# echo * .*
show (or do)?
--
Stefaan A Eeckels
--
Isn't it amazing how a large number of evil morons can give the
appearance of being a single evil genius? --Mel Rimmer
Ron
--ron
ThanksButNo
This happened to me once when I had installed a non-Sun CD-Rom
player in a U10 (trying to get it to work with a DVD. It might
be do-able, but it probably needs a firmware upgrade).
As there was a disk in the CD-rom, the Volume Manager would
core out and make either the /vol or /mnt directories unusable.
(I forget which.) Any variety of "ls /" would hang.
I could "ls" any file or folder in the root directory, except
for the offending directory that was supposed to hold the CD.
Any sort of "ls /" would include the offending directory.
Ewald Ertl suggested running "pstack" on the core file to find
out what process core'd out. That's good advice. If it turns
out that it's the Volume Manager (/usr/sbin/vold), it might be
that you have a removable device (CD, floppy, memory stick, etc.)
that can not be mounted due to a hardware problem or some such.
/:-/