https://bugzilla.novell.com/show_bug.cgi?id=679212 https://bugzilla.novell.com/show_bug.cgi?id=679212#c1 --- Comment #1 from Tommi Nieminen 2011-03-21 16:00:06 UTC --- (In reply to comment #0)

Using this as a clue I managed to pinpoint the problem: the directory /var/lib/nfs has 700 permissions instead of the expected 755: under that directory are subdirectories and files that should be user-readable. Changing the permissions to 755 was enough to get NFS shares mounted at boot time.

OK – now even this isn’t enough. I tried to give go+rX rights to all the files in /var/lib/nfs as well with no results. It looks like the problem is in the rpc.statd part, since that is always started separately when I’m forced to do “sudo mount /nfs_mount_point” at the prompt. -- 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=679212 https://bugzilla.novell.com/show_bug.cgi?id=679212#c3 --- Comment #3 from Tommi Nieminen 2011-03-28 14:12:48 UTC --- (In reply to comment #2)

There must be some reason that the filesystems aren't being mounted.

However is the network configured on this machine? By 'networkmanager' or ifup?

By ifup (wired network), so that rules out the rest of your suggestion. The problem still remains :( -- 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=679212 https://bugzilla.novell.com/show_bug.cgi?id=679212#c5 --- Comment #5 from Tommi Nieminen 2011-03-29 19:57:22 UTC --- Created an attachment (id=422005) --> (http://bugzilla.novell.com/attachment.cgi?id=422005) /etc/fstab -- 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=679212 https://bugzilla.novell.com/show_bug.cgi?id=679212#c7 Robert Nurnberg changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|software@legisign.org | --- Comment #7 from Robert Nurnberg 2011-03-31 12:10:43 UTC --- Created an attachment (id=422452) --> (http://bugzilla.novell.com/attachment.cgi?id=422452) /etc/fstab -- 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=679212 https://bugzilla.novell.com/show_bug.cgi?id=679212#c9 Robert Nurnberg changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |robert.nurnberg@gmx.de --- Comment #9 from Robert Nurnberg 2011-03-31 12:13:45 UTC --- Just to say that I have attached my fstab and nfs files as well. I discovered the same bug on installing openSUSE 11.4 on my machine. Wired network connection. All worked fine on openSUSE 11.2 and 11.3, same hardware, same setup. Did new install with openSUSE 11.4, and since then nfs drives are no longer mounted at boot time. -- 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=679212 https://bugzilla.novell.com/show_bug.cgi?id=679212#c11 --- Comment #11 from Neil Brown 2011-04-06 06:00:06 UTC --- Another thought... Could you please edit /etc/nfsmount.conf, and set "Defaultvers=3". Find the line: # Defaultvers=4 and change it to Defaultvers=3 Then reboot and see if the nfs filesystems get mounted. Thanks. -- 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=679212 https://bugzilla.novell.com/show_bug.cgi?id=679212#c12 --- Comment #12 from Robert Nurnberg 2011-04-06 08:40:33 UTC --- Neil, changing to

Defaultvers=3

did not help. Same behaviour as before. And yes, both the /usr/local and the /home mount fail at boot time. -- 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=679212 https://bugzilla.novell.com/show_bug.cgi?id=679212#c14 --- Comment #14 from Tommi Nieminen 2011-04-06 15:21:39 UTC --- (In reply to comment #11)

Could you please edit /etc/nfsmount.conf, and set "Defaultvers=3".

Find the line:

# Defaultvers=4

and change it to

Defaultvers=3

Then reboot and see if the nfs filesystems get mounted.

Didn’t work for me either. I also tried giving Nfsvers=3 as a server-specific option – that is, I created a “[ Server "habermas" ]” section and added it there, but to no avail. -- 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=679212 https://bugzilla.novell.com/show_bug.cgi?id=679212#c16 --- Comment #16 from Tommi Nieminen 2011-04-07 07:02:46 UTC --- (In reply to comment #15) At the moment I’m on a different machine and this one runs CrunchBang, so my answer is conditional. I’m able to check these when I get home:

Do you get any error messages during boot?

Not constantly. On a wide screen it’s somewhat difficult to say which service reports “Done” and which something else, but at least yesterday when I tried the only service that “Failed” was mcelog – and after another boot even that reported “Done”. I’ve also tried to grep relevant strings (“nfs”, the server name, etc.) from /var/log/* but nothing has shown up.

Do you have IPv6 enabled at all? Do the server names have IPv6 addresses? That probably shouldn't matter, but at the moment any odd details would be worth following up.

I actually suspected this previously, and disabled IPv6 in YaST. No results. After that, I enabled IPv6 again. -- 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=679212 https://bugzilla.novell.com/show_bug.cgi?id=679212#c18 arjan ten hoopen changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arjan.ten.hoopen@zonnet.nl --- Comment #18 from arjan ten hoopen 2011-04-17 18:00:13 UTC --- I have the same problem after I upgraded my 3 clients and one server. I added some echo statements within /etc/init.d/nfs to see what's going on. Here is the output (I guess it's self explanantory if you look at /etc/init.d/nfs ;) ================ begin =============== 19:20:39 Entering 19:20:39 should be able to connect to the srver lets give it a ping ping: unknown host schuurpc 19:20:39 starting nfs cleint services 19:20:41 sm-notify 19:20:41 Mounting network file systems ... 19:20:41 do mount -at nfs,nfs4 mount.nfs: Failed to resolve server schuurpc: No address associated with hostname mount.nfs: Failed to resolve server schuurpc: No address associated with hostname mount.nfs: Failed to resolve server schuurpc: No address associated with hostname mount.nfs: Failed to resolve server schuurpc: No address associated with hostname mount.nfs: Failed to resolve server schuurpc: No address associated with hostname 19:20:41 done of do mount -at nfs,nfs4 19:20:41 what is mounted devtmpfs on /dev type devtmpfs (rw,relatime,size=506992k,nr_inodes=126748,mode=755) tmpfs on /dev/shm type tmpfs (rw,relatime) devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000) /dev/sda6 on / type ext3 (rw,relatime,errors=continue,user_xattr,acl,barrier=1,data=ordered) proc on /proc type proc (rw,relatime) sysfs on /sys type sysfs (rw,relatime) debugfs on /sys/kernel/debug type debugfs (rw,relatime) /dev/sda3 on /boot type ext3 (rw,relatime,errors=continue,user_xattr,acl,barrier=1,data=ordered) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) /dev/sda1 on /windows type fuseblk (ro,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) 19:20:41 above is what is mounted 19:20:41 should be able to connect to the srver lets give it a ping ping: unknown host schuurpc 19:20:41 leaving ================== end ========= I seems that my network is not up (yet). I'm using NIS and the automounter (home directories of users are on the server). After the boot procedure is finished I do get the login prompt, and I get logged in and my home directory is available. So now the network is available ;) However the nfs filesystems in /etc/fstab: schuurpc:/pub /net/SchuurPC/pub nfs defaults 0 0 schuurpc:/mp3 /net/SchuurPC/mp3 nfs defaults 0 0 schuurpc:/tenhoopen /net/SchuurPC/tenhoopen nfs defaults 0 0 schuurpc:/video /net/SchuurPC/video nfs defaults 0 0 schuurpc:/backup /net/SchuurPC/backup nfs defaults 0 0 are NOT!!!! mounted. What is going on. I have this on all my systems. All tips/trics/solutions are appreciated. Arjan -- 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=679212 https://bugzilla.novell.com/show_bug.cgi?id=679212#c20 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |arjan.ten.hoopen@zonnet.nl --- Comment #20 from Neil Brown 2011-04-18 06:03:05 UTC --- Hi Arjan, are you using network-manager to configure your network, or ifup? If network manager, then /etc/NetworkManager/dispatcher.d/nfs should be mounting your filesystems for you. Maybe put some echo >> /tmp/log ..... in there to see what is happening. If you are using ifup, then as network is started at position '02': /etc/init.d/rc5.d/S02network and nfs at position '05' /etc/init.d/rc5.d/S05nfs the network should be up. Maybe put some 'echo's in /etc/init.d/network to find out what is happening in there. -- 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=679212 https://bugzilla.novell.com/show_bug.cgi?id=679212#c22 arjan ten hoopen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|arjan.ten.hoopen@zonnet.nl | --- Comment #22 from arjan ten hoopen 2011-04-25 09:06:45 UTC --- (In reply to comment #20)

Hi Arjan, are you using network-manager to configure your network, or ifup?

If network manager, then /etc/NetworkManager/dispatcher.d/nfs should be mounting your filesystems for you. Maybe put some echo >> /tmp/log ..... in there to see what is happening.

If you are using ifup, then as network is started at position '02':

/etc/init.d/rc5.d/S02network and nfs at position '05' /etc/init.d/rc5.d/S05nfs

the network should be up. Maybe put some 'echo's in /etc/init.d/network to find out what is happening in there.

It turned out that a switch was given my trouble (the system switched to wireless instead). After resetting the switch the problem disappeared. Thanks for the support!! Arjan -- 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=679212 https://bugzilla.novell.com/show_bug.cgi?id=679212#c24 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |software@legisign.org --- Comment #24 from Neil Brown 2011-04-28 02:27:45 UTC --- (In reply to comment #21)

(In reply to comment #17)

...

Turns out that /etc/init.d/nfs was not run at boot time at all. ... I have now activated NFS via YaST -> System -> System Services (Runlevel).

This worked for me too – ONCE, just after the first boot after making the change. On subsequent boots NFS shares are again not mounted.

There’s one difference however: when I now mount the shares manually, I do not get the “Starting rpc.statd... Done” message. Looks like that process is already started.

So it seems that you have two problems. One is that the nfs script wasn't even running - that has been fixed. The other is that when it runs it fails to mount for some reason. Again it would be helpful to look for error messages, possibly as describe in comment #15. Does that reveal anything useful? -- 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=679212 https://bugzilla.novell.com/show_bug.cgi?id=679212#c26 --- Comment #26 from arjan ten hoopen 2011-05-02 14:07:37 UTC --- (In reply to comment #22) I do get the nfs disks mounted however it turns out that it takes minutes (in stead of the expected half-a-second). I added echo statements in /etc/init.d/nfs which resulted into the following output: ================= 14:20:06 Starting NFS client services: 14:20:06 starting sm-notify 14:20:06 sm-notify started 14:20:06 starting idmapd 14:20:06 idmapd started 14:20:06 Mounting network file systems ... 14:20:06 executing udevadm settle 14:23:00 udevadm settle done 14:23:00 now mount -at nfs,nfs4 Starting rpc.statd .....done 14:23:02 mount -at nfs,nfs4 done ================= As you can see "udevadm settle" takes almost 3 minutes. Does this make sence? The server is a 32bit 11.4 system, the client is a 64bit 11.4 system. Any suggestions ... Arjan -- 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=679212 https://bugzilla.novell.com/show_bug.cgi?id=679212#c28 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |lnussel@novell.com InfoProvider|lnussel@novell.com | --- Comment #28 from Ludwig Nussel 2011-05-16 09:20:31 CEST --- On distro upgrade the nfs service stays enabled if it was enabled before. New installs have it off, that's correct. Having nfs on slows down the boot process as it causes a dependency of $remote_fs on network which is unnecessary in the majority of installations. If yast is used to add nfs shares to fstab it makes sure to also enable 'nfs'. Manually editing /etc/fstab requires a manual "chkconfig nfs on" of course. -- 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=679212 https://bugzilla.novell.com/show_bug.cgi?id=679212#c30 --- Comment #30 from Bernhard Wiedemann 2011-06-15 23:18:37 CEST --- This is an autogenerated message for OBS integration: This bug (679212) was mentioned in https://build.opensuse.org/request/show/73652 11.4 / release-notes-openSUSE -- 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.