https://bugzilla.novell.com/show_bug.cgi?id=420575 User jpr@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=420575#c1 JP Rosevear changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kde-maintainers@suse.de |nfbrown@novell.com Component|KDE3 |Basesystem --- Comment #1 from JP Rosevear 2008-09-18 11:33:22 MDT --- Well, I think this is a general nfs issue with networking going down, the nfs maintainer can probably give more background, but I'm not sure its easy to fix. -- 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.

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.

https://bugzilla.novell.com/show_bug.cgi?id=420575 User nfbrown@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=420575#c5 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nfbrown@novell.com --- Comment #5 from Neil Brown 2008-09-24 22:29:58 MDT --- What filesystem(s) do you have mounted over NFS? Are they mounted via /etc/fstab or by and automounter. What mount options are used? If an NFS filesystem is mounted in /etc/fstab without the 'bg' option, I would expect a delay at boot-time. There shouldn't be a delay if you have 'bg'. Switching from wired to wireless would work if you used UDP, but I don't think it would ever work with TCP. I don't think 10.3 defaulted to UDP. I don't suppose you still have your 10.3 installation that you can check? Unplugging the NIC cable would only cause a hang when something accessed the filesystem. Maybe something is accessing filesystems in 11.0 in a way that wasn't happening in 10.3. Maybe the answers to the above three questions will help make the situation clearer. Looking forward: if you want NFS to work at all reliably while your laptop changes IP address, you would really need to set up something like OpenVPN so your laptop can have a stable address (on the VPN) while it changes network. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=420575 User quentin.jackson@exclamation.co.nz added comment https://bugzilla.novell.com/show_bug.cgi?id=420575#c6 --- Comment #6 from Quentin Jackson 2008-09-26 16:15:43 MDT --- I have xfs filesystems on a software raid 5 mounted over NFS, they are set up by the NFS client tool in YaST and effectively end up in /etc/fstab therefore. No idea how else to do it :) The entries copied from fstab are: 192.168.1.10:/home/username /home/quentinj/NFS/username nfs defaults 0 0 192.168.1.10:/mnt/data1/Video /home/quentinj/NFS/Video nfs defaults 0 0 192.168.1.10:/mnt/data1/Audio /home/quentinj/NFS/Audio nfs defaults 0 0 192.168.1.10:/mnt/data1/MyPics /home/quentinj/NFS/MyPics nfs defaults 0 0 Hadn't heard of the bg option before, should that be added so that YaST adds it automatically here or does it cause other side effects? I have never knowingly used UDP or TCP specifically for NFS and I don't have the 10.3 any more sorry, though I would install it if I wasn't so scared I'd get burnt by the beta 1 grub problem that I was lucky to get around! :) What I do know is that there were quite a few new problems with NFS in OpenSuSE 11.0 and to date I still turn off NFS 4 options as I cannot get a connection with them, so I still find the NFS stuff suspicious. I also notice interesting behaviour with the network manager in that nowadays it maintains 2 simultaneous connections rather than switching between the two and I don't think it updates the correct route to send traffic through. Wireless doesn't even work for me since beta 1 so I can't test it any longer anyway. I just tried replicating the unplugging of the NIC card and the PC didn't crash, it used to on 11.0 (a seperate machine I've got) so I guess that's been fixed via network update. Looking forward no one is going to set up a vpn to get NFS working sorry. The suggestion higher up to have network manager unmount and remount sounds more doable though. Hey, windows can do it, Linux should be able to do it much easier! ;) -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=420575 User quentin.jackson@exclamation.co.nz added comment https://bugzilla.novell.com/show_bug.cgi?id=420575#c8 Quentin Jackson changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|quentin.jackson@exclamation.co.nz | --- Comment #8 from Quentin Jackson 2008-12-04 16:36:18 MST --- Thanks, it kind of works. I don't get all the horrible system freezes any more, but when switching from wired to wireless it doesn't remount, I have to do that manually. So it appears we're half way there, but certainly a big improvement, thanks! Q -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=420575 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=420575#c10 Tambet Ingo changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tambet@novell.com Status|NEEDINFO |NEW Info Provider|tambet@novell.com | --- Comment #10 from Tambet Ingo 2008-12-05 01:17:38 MST --- That's what it already does: /etc/init.d/nfs restart -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=420575 User quentin.jackson@exclamation.co.nz added comment https://bugzilla.novell.com/show_bug.cgi?id=420575#c12 Quentin Jackson changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|quentin.jackson@exclamation.co.nz | --- Comment #12 from Quentin Jackson 2008-12-08 15:06:55 MST --- Great timing :) I actually did this just this morning before getting on the plane. The thing is that it's between switching wireless and wired which makes it impossible to put a delay in as it is done automatically. Restarting the NFS service definately fixes it. I think we're on the same wavelength cause' this morning I was thinking it needed a slight delay before restarting the services. It seems to take about 5-10 seconds for either wireless or wired network to come up, so maybe we can delay the NFS restart a little? Or maybe it's not running after connection confimation is obtained from network manager? Q -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=420575 User nfbrown@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=420575#c14 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |quentin.jackson@exclamation.co.nz --- Comment #14 from Neil Brown 2008-12-10 16:14:06 MST --- Setting to NEEDINFO - see previous comment. -- 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.