Bug 82603 - NFS Clients hang forever when trying to reboot them while an nfs server is down.
NFS Clients hang forever when trying to reboot them while an nfs server is down.
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: nfs-utils (Show other bugs)
7.3
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Steve Dickson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-01-23 17:22 EST by Glen
Modified: 2007-04-18 12:50 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-06-15 17:20:20 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Glen 2003-01-23 17:22:06 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/20020809

Description of problem:
If one of our nfs servers goes down and while it is down we try and reboot one
of the nfs clients, then the client will hang forever when it tries to unmount
the nfs drives.  Actually, I guess I can't say forever, but I've waited many
many hours for something to time out but I'm always forced to just reset the
systems.  None of this happened until we started using the hard mount option. 
But we can't use the soft mount option because with soft mounts the jobs we run
on our various servers are more likely to crash.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Set up an nfs client and server with the hard mount option.
2.Shut down the server.
3.Try and reboot the client.
    

Actual Results:  The client will hang when it tries to unmount the nfs drives.

Expected Results:  The client will hang when it tries to unmount the nfs drives.

Additional info:
Comment 1 Glen 2003-03-06 15:37:02 EST
I installed the new 2.4.18-24 kernel on all my machines and that fixed this problem.

Note You need to log in before you can comment on or make changes to this bug.