[SOLVED] df -h suddenly delaying

elliot01 · 12-15-2009, 10:17 AM

Hi all,

Maybe I am worrying about nothing here, but I have a CentOS 5.3 box (running Scalix). It's a Dell server with RAID1 setup.

'df -h' produces this:

Code:

[root@mail1 log]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
                      220G   13G  197G   6% /
/dev/sda1              99M   25M   70M  26% /boot
tmpfs                 2.0G     0  2.0G   0% /dev/shm

I built this system about 6 months ago (production environment), and I added this command to root's .bash_profile so I could keep an eye on the drive usage.

I log into it most days and always found the 'df' command to return to the command prompt pretty much instantly (I admin about 10 other linux servers which behave the same).

But... over the past couple of days, the command stalls after printing the results, for about 18 seconds before showing the command prompt.

This happens upon immediate connection (ie: from bash_profile) or whether I am already at the prompt and type the command manually.

I am worried that there could be a potential drive issue - this would be majorly bad! No log files are pumping out anything recently regarding relevant issues (that I can see).

Could someone suggest where I should start, in diagnosing whether I have a problem or not? I have only got into Linux over the past two years and am just self-taught, so there are plenty of newbie things I haven't picked up yet.

P.S. The server is miles away, in a secure data centre.

Thanks in advance!

elliot01 · 12-15-2009, 10:20 AM

As soon as I clicked send I had a brainwave!

There was a mounted drive in /mnt which required a 'umount -l /mnt/drivename'.

Well I proved how much I have to learn, but maybe this will help someone in the future?

Thanks anyway for the awesome forum.

TB0ne · 12-15-2009, 12:13 PM

Quote:

Originally Posted by elliot01

As soon as I clicked send I had a brainwave!

There was a mounted drive in /mnt which required a 'umount -l /mnt/drivename'.

Well I proved how much I have to learn, but maybe this will help someone in the future?

Thanks anyway for the awesome forum.

Thanks for coming back and posting the solution, and what worked. I wish more folks did that...