Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#7368 - NFS remount bug fix
Attached to Project:
Arch Linux
Opened by slackhack (slackhack) - Tuesday, 05 June 2007, 16:43 GMT
Last edited by Roman Kyrylych (Romashka) - Tuesday, 25 September 2007, 09:19 GMT
Opened by slackhack (slackhack) - Tuesday, 05 June 2007, 16:43 GMT
Last edited by Roman Kyrylych (Romashka) - Tuesday, 25 September 2007, 09:19 GMT
|
Detailsclients don't remount NFS shares with usable permissions after server reboot or restart of the daemon. the problem lies the exportfs -ua command which doesn't allow reconnection, gives "stale file" error, etc.
reworked nfsd initscript by shazeal fixes the problem (nfsd.mod -- attached). see this thread for more details: http://bbs.archlinux.org/viewtopic.php?id=33582 |
This task depends upon
nfsd.mod
Adding the exportfs -ua command alone did not fix the problem. The second issue was that the 2.6 kernels use proc to store/read the xtab information and the xtab in /var/lib/nfs was not being used on startup.
The reload part is used to clear connections while the nfsd is already running. Used more for testing while I was figuring this out but I guess it could be useful.
I picked this up in June, so apologies for the delay.