Bug 161456
Summary: | nfs mount hangs at boot | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Terry Riley <terrence> |
Component: | nfs-utils | Assignee: | Steve Dickson <steved> |
Status: | CLOSED CANTFIX | QA Contact: | Ben Levenson <benl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | deerfieldtech, starback |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-03-10 18:46:40 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Terry Riley
2005-06-23 15:34:35 UTC
Same problem here. I see some activity on NFS issues in fedora-list as well. For reference I switched off selinux, no change. I am exporting home directories from my server to my local net, 192.168.0.0/24 . I also happen to be using firestarter on my server as my firewall interface, using the dhcp function, and I notice that even if I shut off a machine, it is still shown as an active nfs connection. If I restart NFS services on the server, the active connection is dropped, and then my workstation machine will boot correctly and import the NFS home export. Would it be possible to get an b2zip-ed binary ethereal trace (i.e. on the client 'tethereal -w /tmp/data.pcap host server')? Closing because bug has remained in NEEDINFO state without reply for a long period of time. Note that FC3 and FC4 are supported by Fedora Legacy for security fixes only. Please install a still supported version and retest. If it still occurs on FC5 or FC6, please reopen and assign to the correct version. Otherwise, if this a security issue, please change the product to Fedora Legacy. Thanks, and we are sorry that we did not get to this bug earlier. This bug was originally filed against a much earlier version of Fedora Core, and significant changes have taken place since the last version for which this bug is confirmed. |