https://bugzilla.novell.com/show_bug.cgi?id=420575
User nfbrown@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=420575#c3
Neil Brown changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|nfbrown@novell.com |bnc-team-screening@forge.provo.novell.com
--- Comment #3 from Neil Brown 2008-09-21 18:32:48 MDT ---
NFS doesn't cope with the client's IP address changing.
One option is to use UDP for mounting rather than TCP (-o udp).
In this configuration, changing the client address causes fewer problems.
However there are other problems with using UDP, such as a small
possibility of data corruption, particularly at high data rates.
In either case, if you hold any locks on NFS files before changing
IP address, you probably will having significant problems accessing those
files after the change.
Probably the best approach would be to have all NFS filesystems mounted
by an auto-mounted, and have Network Manager unmount any NFS filesystems
before changing the IP address. This would need to be a --lazy unmount
in case some process were using the filesystem. That process would
probably hang, but any other process that tried to access the filesystem
would we a new mount.
I think that it would always be a good idea for NetworkManager to
unmount --lazy any NFS filesystem when changing IP address, because they
will be completely useless and can be harmful.
This should not include NFS filesystems that are mounted via the loopback
address (127.0.0.1) or top-level mounts of the auto-mounter.
As a longer term response I will look into the possibility of enabling
an NFS mount to move smoothly to a new client IP address, but at this
stage I think that situation is best handed by NetworkManager.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.