[ale] SLES 11 SP4 df

[James Taylor]

unloading the nfs client will normally clear the hang.
-jt
 
 

James Taylor
678-697-9420
james.taylor at eastcobbgroup.com



>>> "Raj Wurttemberg" <rajaw at c64.us> 8/25/2016 11:27 PM >>> 
I have had that happen in my NFS environments on RHEL6 as well. I was
only able to regain control of the system again after finding the
off-line NFS mount. These are my current NFS mount options in my fstab:

 

rw,bg,rsize=65536,wsize=65536,hard,nfsvers=3,nointr,nosharecache,timeo=600,tcp

 

(yes, I am aware that ‘nointr’ is depreciated and ‘timeo=600’
is the default… not my idea to include them.)

 

/Raj

 

 

From: ale-bounces at ale.org [mailto:ale-bounces at ale.org] On Behalf Of
Brian Stanaland
Sent: Thursday, August 25, 2016 7:23 PM
To: Atlanta Linux Enthusiasts - Yes! We run Linux! <ale at ale.org>
Subject: [ale] SLES 11 SP4 df

 

Has anyone run across this situation?

It seems the df command in sles 11 sp4 stats all the filesystems before
displaying anything. This means that when it gets stuck on a network
file system it just stops doing anything. It's waiting for a reply from
the file system that will never come. The user knows something is wrong
but if it displayed results as it went along, they'd know which file
system isn't responding. 

--Brian



-- 

"Anyone who has never made a mistake has never tried anything new."
-Albert Einstein