Bug 180856
Summary: | kernel errors hanging nfsd | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Daniele Branchini <dbranchini> |
Component: | kernel | Assignee: | Steve Dickson <steved> |
Status: | CLOSED WORKSFORME | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | bmarson, davej, sct, wtogami |
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: | 2006-09-18 08:25:59 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
Daniele Branchini
2006-02-10 09:55:58 UTC
>Now it seems to automatically recover in some way,
>since I see the errors but nfs is actually working.
This was untrue. After two more errors like the one above, I have this situation:
[root@adone ~]# service nfs status
Arresto di NFS mountd: rpc.mountd (pid 31571) in esecuzione...
nfsd interrotto
rpc.rquotad (pid 31568) in esecuzione...
[root@adone ~]# service nfs restart
Arresto di NFS mountd: [ OK ]
Arresto del demone NFS: [FALLITO]
Arresto di quotas NFS: [ OK ]
Arresto dei servizi NFS: [ OK ]
Avvio dei servizi NFS: [ OK ]
Avvio di quotas NFS: [ OK ]
Avvio demone NFS: [ OK ]
Avvio di NFS mountd: [ OK ]
[root@adone ~]# tail /var/log/messages
Feb 13 11:21:19 adone rpc.mountd: Caught signal 15, un-registering and exiting.
Feb 13 11:21:20 adone nfsd[31569]: nfssvc: Setting version failed: errno 16
(Device or resource busy)
Feb 13 11:21:20 adone rpc.idmapd: nfsdreopen: Opening '' failed: errno 2 (No
such file or directory)
[root@adone ~]# service nfs status
Arresto di NFS mountd: rpc.mountd (pid 31571) in esecuzione...
nfsd interrotto
rpc.rquotad (pid 31568) in esecuzione...
- Still having problems under 2.6.16-1.2069 - Bugs happen when trying to copy relatively large amount of data (about 500mb) - The partition I'm actually exporting is 1.6 Tb, ext3. Everybody told me is a dumb thing to use ext3 for such a huge partition, but I'm unable to change the filesystem until I get another subsystem for backup. Could my problems be related to this? ext3 on FC4 should be safe up to 8TB, and has been tested on such systems, so I have no reason to think that any NFS errors are related to the large ext3 fs. [This comment added as part of a mass-update to all open FC4 kernel bugs] FC4 has now transitioned to the Fedora legacy project, which will continue to release security related updates for the kernel. As this bug is not security related, it is unlikely to be fixed in an update for FC4, and has been migrated to FC5. Please retest with Fedora Core 5. Thank you. Eventually I found out that the problem was referable to an old alpha tru64 machine that was mounting the nfs partition. I needed badly to keep the server going, so I just removed that client from /etc/exports . At this point I can't tell if the problem was ascribable to the architecture of that particular nfs client or its net situation (a little bit messy) or maybe the whole thing was actually regarding some kernel bug. I'm changing this bug to "WORKSFORME", since I'm unable to do further investigations... Thank you very much Stephen for the information about large ext3 fs. Some dumb colleague told me that it was the main cause of my problems. |