[opensuse] SuSE 13.1 as NFS client: boot hangs
Hello, I had this on my SuSE machines since SuSE 10.3, always without problems: A NAS acts as NFS server and my SuSE machine as NFS client. I simply create some mount directories and let yast2 do the magic in creating the connection between NAS as NFS server and machine as NFS client. I never touched any NFS config files as it worked out of the box as it should be. Now I changed to SuSE 13.1, did the same as always and it hangs at a certain time when booting. :-(((( After I switch on the NAS, the boot goes on. What is that hickup? I just use the default yast2 settings as with every SuSE before. After deleting the NFS shares in Yast2 there is only one share that appears in df -k I unmount that and the next one appears. I unmount the 2nd and the 3rd appears ->? In previous versions of SuSE "df -k" always showed all NFS shares! In this forum there are other problems with NFS but afaics not this one. Internet is not helpful. https://en.opensuse.org/YaST_NFS_Client says "Boot times increased while waiting for a response from network NFS servers. This was resolved with full systemd which simply bypasses unavailable drives using short timeouts and then connects when drives become available. " Is that broken? Any pointers? Thx -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 02 Jul 2014 20:38:59 +0200
MarkusGMX
Hello,
I had this on my SuSE machines since SuSE 10.3, always without problems:
A NAS acts as NFS server and my SuSE machine as NFS client. I simply create some mount directories and let yast2 do the magic in creating the connection between NAS as NFS server and machine as NFS client. I never touched any NFS config files as it worked out of the box as it should be.
Now I changed to SuSE 13.1, did the same as always and it hangs at a certain time when booting. :-((((
After I switch on the NAS, the boot goes on.
What is that hickup? I just use the default yast2 settings as with every SuSE before.
read the fine nfs(5) manual. at least two fstab options are of particular interest: soft/hard and retry. Note that retry's default is 10000 minutes, almost a full week. Have you waited for 10000 minutes to see if it's actually hung? [snip]
Is that broken?
Who knows? nfs has changed behaviour significantly over the years for various reasons.
Any pointers?
Try different combinations of soft/hard and retry, for one, and other options that also that seem relevant. YMMV. Heed the warnings in the manpage and don't do anything that may lose data until you're happy with the settings. jd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 04/07/14 03:04, schrieb jdebert:
On Wed, 02 Jul 2014 20:38:59 +0200 MarkusGMX
wrote: Hello,
I had this on my SuSE machines since SuSE 10.3, always without problems:
A NAS acts as NFS server and my SuSE machine as NFS client. I simply create some mount directories and let yast2 do the magic in creating the connection between NAS as NFS server and machine as NFS client. I never touched any NFS config files as it worked out of the box as it should be.
Now I changed to SuSE 13.1, did the same as always and it hangs at a certain time when booting. :-((((
After I switch on the NAS, the boot goes on.
What is that hickup? I just use the default yast2 settings as with every SuSE before.
read the fine nfs(5) manual. at least two fstab options are of particular interest: soft/hard and retry. Note that retry's default is 10000 minutes, almost a full week. Have you waited for 10000 minutes to see if it's actually hung?
I tweaked the following options in /etc/nfsmount.conf : Retry=0 (was 2) Timeo=300 (was 600) _netdev in /etc/fstab, all together now : ...nfs defaults,_netdev 0 0 Now boot is much faster but the whole stuff hangs after login into KDE. :-( I do not know where to go on and why KDE4 hangs with NFS now. :-( This is really annoying especially since all this worked for years in previous versions.
[snip]
Is that broken?
Who knows? nfs has changed behaviour significantly over the years for various reasons.
Any pointers?
Try different combinations of soft/hard and retry, for one, and other options that also that seem relevant. YMMV. Heed the warnings in the manpage and don't do anything that may lose data until you're happy with the settings.
The above tweaks should only affect the situation when NFS is completely missing. Thx in advance -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 13 Jul 2014 23:06:27 +0200
MarkusGMX
Am 04/07/14 03:04, schrieb jdebert:
On Wed, 02 Jul 2014 20:38:59 +0200 MarkusGMX
wrote: Hello,
I had this on my SuSE machines since SuSE 10.3, always without problems:
A NAS acts as NFS server and my SuSE machine as NFS client. I simply create some mount directories and let yast2 do the magic in creating the connection between NAS as NFS server and machine as NFS client. I never touched any NFS config files as it worked out of the box as it should be.
Now I changed to SuSE 13.1, did the same as always and it hangs at a certain time when booting. :-((((
After I switch on the NAS, the boot goes on.
What is that hickup? I just use the default yast2 settings as with every SuSE before.
read the fine nfs(5) manual. at least two fstab options are of particular interest: soft/hard and retry. Note that retry's default is 10000 minutes, almost a full week. Have you waited for 10000 minutes to see if it's actually hung?
I tweaked the following options in /etc/nfsmount.conf : Retry=0 (was 2) Timeo=300 (was 600)
_netdev in /etc/fstab, all together now : ...nfs defaults,_netdev 0 0
Now boot is much faster but the whole stuff hangs after login into KDE. :-(
. Perhaps try using the tcp protocol option, 'Proto=TCP' in nfsmount.conf under either the global or server-specific sections? I have a ARM-based client that hangs after mounting nfs using defaults, solved using IPv4 tcp instead of default udp. If it's using IPv6 try using IPv4 -- udp4 or tcp4 instead. I don't use KDE4. Sorry. jd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 14/07/14 01:42, schrieb jdebert:
On Sun, 13 Jul 2014 23:06:27 +0200 MarkusGMX
wrote: Am 04/07/14 03:04, schrieb jdebert:
On Wed, 02 Jul 2014 20:38:59 +0200 MarkusGMX
wrote: Hello,
I had this on my SuSE machines since SuSE 10.3, always without problems:
A NAS acts as NFS server and my SuSE machine as NFS client. I simply create some mount directories and let yast2 do the magic in creating the connection between NAS as NFS server and machine as NFS client. I never touched any NFS config files as it worked out of the box as it should be.
Now I changed to SuSE 13.1, did the same as always and it hangs at a certain time when booting. :-((((
After I switch on the NAS, the boot goes on.
What is that hickup? I just use the default yast2 settings as with every SuSE before.
read the fine nfs(5) manual. at least two fstab options are of particular interest: soft/hard and retry. Note that retry's default is 10000 minutes, almost a full week. Have you waited for 10000 minutes to see if it's actually hung?
I tweaked the following options in /etc/nfsmount.conf : Retry=0 (was 2) Timeo=300 (was 600)
_netdev in /etc/fstab, all together now : ...nfs defaults,_netdev 0 0
Now boot is much faster but the whole stuff hangs after login into KDE. :-(
Perhaps try using the tcp protocol option, 'Proto=TCP' in nfsmount.conf under either the global or server-specific sections? I have a ARM-based client that hangs after mounting nfs using defaults, solved using IPv4 tcp instead of default udp. If it's using IPv6 try using IPv4 -- udp4 or tcp4 instead.
I don't use KDE4. Sorry.
_netdev is gone after the changes and trials I did. I finally solved it by not mounting it under /media/NASdir1 /media/NASdir2 but by making a directory in between and mounting it this way: /media/NAS/dir1 /media/NAS/dir2 and so on. It is not obvious to me why that makes a difference but anyway with that and the changed timings it does not hang at boot time and it does not hang after login to KDE4. Boot logging now says: [FAILED] Failed to mount /media/NAS/dir1. See 'systemctl status media-NAS-dir1.mount' for details. [DEPEND] Dependency failed for Remote File Systems. [DEPEND] Dependency failed for Postfix Mail Transport Agent. ... [FAILED] Failed to mount /media/NAS/dir2. See 'systemctl status media-NAS-dir2.mount' for details. ... [FAILED] Failed to mount /media/NAS/dir3. See 'systemctl status media-NAS-dir3.mount' for details. So this is solved...somehow. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 20 Jul 2014 14:17:52 +0200
MarkusGMX
So this is solved...somehow.
Yes, sounds too familiar wrt nfs. Lacking detailed info, I just keep trying different things until it works.(^_^) Interesting that you've managed to get static mount points under /media without problems. When I tried, before 12.3, it failed for several annoying reasons. Finally used /mnt for all the static and manual mounts. Hope it behaves well for you! jd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2014-07-24 a las 17:23 -0700, jdebert escribió:
So this is solved...somehow.
Yes, sounds too familiar wrt nfs. Lacking detailed info, I just keep trying different things until it works.(^_^)
Interesting that you've managed to get static mount points under /media without problems. When I tried, before 12.3, it failed for several annoying reasons. Finally used /mnt for all the static and manual mounts.
Hope it behaves well for you!
Not surprising at all. Not surprised that it did not work for you time ago, and not surprised that it now works >:-) Ok, in general, you should avoid using mount points under "/media", because that directory is typically used by automount systems, and because the directory is/was, depending on release, volatile and/or erased at boot. So better consider it off-limits. Use "/mnt" instead. Why it works now? Because now the automatics prefer to use "/run/user/something" instead, unless you do certain change that uses "/media" again. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlPRugoACgkQja8UbcUWM1wv5AD/VBXvjXbtGZz1ds7uXP5sS2Yv /RGiVCtVAs/BbN1n9JgA/jkBn2glia52EVIVfDZBhnT1n/tQ5ZdwLx0QD3ZzkvvU =0IsI -----END PGP SIGNATURE-----
participants (3)
-
Carlos E. R.
-
jdebert
-
MarkusGMX