On Sun, 13 Jul 2014 23:06:27 +0200 MarkusGMX <Markus.Egg@gmx.at> wrote:
Am 04/07/14 03:04, schrieb jdebert:
On Wed, 02 Jul 2014 20:38:59 +0200 MarkusGMX <Markus.Egg@gmx.at> 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