Re: Is my directory corrupted?
From: Moe Trin (ibuprofin_at_painkiller.example.tld)
Date: Mon, 06 Jun 2005 19:37:38 -0500
In the Usenet newsgroup alt.os.linux, in article
<firstname.lastname@example.org>, craig wrote:
>Running Fedora 3 with most recent updates for now probably 8 months or
>when ever it was first released.
08 Nov 2004. Did it have the problem in the past? If so, what did you
>Now I discover:
>Command line command such as # ls -d */
>there is a long 31 sec delay before it generates the results to the screen.
Does the octothorpe in front of the command imply you are running as root?
That is a hazardous mode, and you should only be root when absolutely
necessary. If this is as root, how does it work as a normal user?
Well, a lot is going to depend on what's in the directories you are
trying to look at. Are there a lot of directories? Are any of them Samba
mounts? Does 'ls -d /*' show the 10 to 20 directories normally found in
root virtually instantly? Does 'alias' return anything relating to ls?
31 seconds is a heck of a long time - I don't know how it might be
connected to hostnames, but does the 'hostname' command return a full
hostname with dots and a domain? Is that full hostname in /etc/hosts?
If not, does a DNS query return the full name/address pair in both
directions (IP to name, name to IP)?
>What's up? what's causing this. A fresh boot doesn't change a thing.
Rebooting rarely has any effect on *nix, except to imperceptibly slow
it down because the memory cache is emptied.
Another random thought - as root, run the command 'rpm -Va > files2check'
This is going to take a couple of minutes to run. Then look at that file,
and compare the output to the 'rpm' man page under VERIFICATION. It is
normal to see some changes - mainly configuration files, and changes in
file ownership. On this system, about 90 "files" get listed (a work
station with about 330 packages installed).