https://bugzilla.novell.com/show_bug.cgi?id=694461 https://bugzilla.novell.com/show_bug.cgi?id=694461#c1 Bruno Friedmann changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bruno@ioda-net.ch --- Comment #1 from Bruno Friedmann 2011-05-18 06:15:00 UTC --- Same here with a ipv6 nfs server. Once booted a rcnfs restart mount everything fine. 11.4, with boot parallel yes -- 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=694461 https://bugzilla.novell.com/show_bug.cgi?id=694461#c2 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nfbrown@novell.com AssignedTo|nfbrown@novell.com |ro@novell.com --- Comment #2 from Neil Brown 2011-05-24 00:12:18 UTC --- This isn't an NFS problem exactly. Rather it is a problem wit /etc/init.d/boot.localfs The "mount" command in the "list_missed" function is trying to mount nfs filesystems (which is strange in itself) and that call mount.nfs mount.nfs is producing some error message (which given the lack of network is not strange), and list_missed isn't filtering that out so "mount.nfs:" is getting reported as a device that doesn't exist yet - which is clearly silly. It could be fixed by adding: mount.nfs:* ) continue ;; # messages from mount into the 'case' statement. Or by adding -t $nofs to the mount command maybe.... Though that "nofs" thing looks wrong. It puts 'no' in front of each type, but the man page says you only need 'no' in front of the first type (though the source suggests that both work). Anyway there is something wrong in boot.localfs and as Rudi is the maintainer .. reassigning to Rudi. -- 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=694461 https://bugzilla.novell.com/show_bug.cgi?id=694461#c4 Martin Soltau changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |smartysmart34@web.de --- Comment #4 from Martin Soltau 2011-05-26 09:41:10 UTC --- Same here. I tried with the nfs-mounts in fstab put on "noauto". In this case the timeout does not occur but ofcourse the mounts are missing and they have to be mounted manually -> ugly solution. I hope there will be a fix soon (through the update-repo). I am not too much into fumbling with these files by myself... Cheers, Martin -- 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=694461 https://bugzilla.novell.com/show_bug.cgi?id=694461#c6 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |werner@novell.com InfoProvider|werner@novell.com | --- Comment #6 from Dr. Werner Fink 2011-05-26 11:09:06 UTC --- The correct line in list_missed() looks like local mount_opts="-t no${tmpfs//,/,no},$nofs -O no_netdev -O nonofail" or after an automatic update local mount_opts="-t no${tmpfs//,/,no},$nofs,nonone -O no_netdev -O nonofail" .. I'd like to know, why this is missed now? It should be noted that $nofs includes not only network based file shares but also mempry based file systems found in /proc/filesystems -- 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=694461 https://bugzilla.novell.com/show_bug.cgi?id=694461#c8 --- Comment #8 from Martin Soltau 2011-06-01 12:47:39 UTC --- Hi all, any news on this one? When I saw the reply of Werner Fink I was hoping for a quick fix because the solution seemed to be quite easy:

local mount_opts="-t no${tmpfs//,/,no},$nofs -O no_netdev -O nonofail"

But after having read "It should be noted that $nofs includes not only network based file shares..." I am now asking myself: Could I just move the above line into /boot.localfs or would I face other major difficulties? Is there more to it then just making the line look like in Suse 11.2 or 11.3? I would be very glad to read about the current status of the solution and maybe a short comment on whether I could fix this with the above line until a fix is rolled out. Kind regards, Martin -- 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=694461 https://bugzilla.novell.com/show_bug.cgi?id=694461#c10 Markus Hilt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mhilt@gmx.de --- Comment #10 from Markus Hilt 2011-07-05 08:40:59 UTC --- Hi all, I have 'solved' this problem on my systems by adding 'mount -a' to the '/etc/init.d/after.local'. So the system will remount all filesystems 'after all scripts of a runlevel have been executed'. Best regards, Markus -- 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=694461 https://bugzilla.novell.com/show_bug.cgi?id=694461#c12 LLL Active changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |LActive@GMX.Net --- Comment #12 from LLL Active 2011-07-06 12:57:33 UTC --- On my terminal ctrl-alt-F1 at boot time, I see that my eth0 & eth1 is being configured before the nfs is started. One is onboard to the mobo, the other a PCI card. I have, however, a WLan card that has the actual network, which gets configured after the nfs is started. So if the system is hard wired by ethernet cable, it works. It does not work with WLan cards, because they seem to be configured after nfs is started. -- 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.