https://bugzilla.novell.com/show_bug.cgi?id=819515 https://bugzilla.novell.com/show_bug.cgi?id=819515#c Jiri Srain changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Bootloader |Basesystem AssignedTo|jsrain@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com QAContact|jsrain@suse.com |qa-bugs@suse.de -- 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=819515 https://bugzilla.novell.com/show_bug.cgi?id=819515#c FeiXiang Zhang changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |nfbrown@suse.com |ovo.novell.com | -- 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=819515 https://bugzilla.novell.com/show_bug.cgi?id=819515#c3 --- Comment #3 from Scott Couston 2013-05-20 13:18:14 EST --- (In reply to comment #2)

If you have filesystems listed in /etc/fstab, then the correct thing for the boot process to do is to wait for all the filesystems to be available before continuing.

If you don't want that then you have 2 options. 1/ add the "bg" option to the NFS mounts in /etc/fstab. This will cause the mount to be attempted once with a fairly short timeout, and if that fails, to continue attempting in the back ground and let the system boot complete.

2/ use an automounter to have the NFS filesystem only mounted on demand. That way an unavailable NFS server will only block the applications that need it, not the whole system.

If you have hard mount requests for NFS filesystem in /etc/fstab, but expect the system to boot when the server is not available, then that is a configuration error.

I didn't really create this is a bug to help myself only. The issue is the default setting after using Yast>Network Services both >>NFS Server and Client are totally inadequate and create the illusion, to the user, the PC has frozen. If there are options let us put them in Yast GUI but as a default something has to change. If at time of boot the NFS Server and/or client is not available;sure wait a reasonable time like 6 seconds but dont stall the whole boot process of a PC to the point users think that their PC has frozen. The issue of NFS v4 or not using is is not clear in help. The option to use GSS Security is totally unclear. With respect to services being activating and being run as PART of the kernel with respect to NFS drives; I didn't make clear. I dont understand why, with Network Drives (mount points) that the kernel cannot monitor ALL Network mount points and exported services! If any become available after boot; or unavailable, the kernel should auto mount or auto dismount as a dynamic property. We shouldn't need services to be running to accomplish. To solve this reoccurring problem, can we just have a default that mounts if its there or waits 6 or so seconds and if not there continue the boot process - Its as simple as that! When we work out what to do with Yast in the future we can add the options in the GUI...Users just want it to work. Admins expect Yast GUI to offer clear choices and all options and simple WORK - NOTHING MORE.. WE can no longer sit between editing files and have GUI's that accomplish everything an admin wants to do...Hate it or not; but the GUI just simply has to work! -- 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=819515 https://bugzilla.novell.com/show_bug.cgi?id=819515#c5 --- Comment #5 from Scott Couston 2013-06-11 07:20:05 EST --- (In reply to comment #4)

So it seems you really issue is with Yast. Consequently I am reassigning this to yast developers.

Main issues seem to be: - autofs is much better for mounting NFS filesystems than /etc/fstab. It should be possible and easy to configure NFS mounts to use autofs - if /etc/fstab is to be used, the "bg" option should be available so that missing servers don't cause the boot to hang.

There might be others that I missed.

Thank you so much for ageing to commit manpower to this problem. This bug goes back to 10.3 and this is the first commitment of resources and for that, I thank you. I dont think any NETWORK drive should be written to /etc/fstab. Auto fs should sit and wait for NFS drives to become present and then not present. If a network drive becomes available, auto mount, the when not available auto dismount and so forth. I think the NFS Server needs to advertise relentlessly and if NFS clients become online the drive is auto mounted. The ability to run application over a NFS drive is perfectly wonderful right now. I run Evolution and all locally held data is on an NFS drive. It makes backing up data from a single source very easy to manage. Its a small data server concept that can be hugely taken advantage of Most of Yast no-loner or has never worked, take Security Centre and Hardening in Yast. under Miscellaneous change the file permission to 'secure' or 'paranoid' and the PC dead and destroyed and not able to be backed out of. Again, thank you for the commitment of resources in this one small area -- 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=819515 https://bugzilla.novell.com/show_bug.cgi?id=819515#c7 --- Comment #7 from Scott Couston 2013-06-12 04:27:53 EST --- Neil, Im just glad someone is going to look at it. I'm happy that the bug wasn't immediately closed as WINTFIX. I'm still querulous as to why the huge amounts of bugs that have been in Yast for going back to 11.0 are never looked into; as most all are closed as WONTFIX. Either your creating a brand new Yast to interface seamlessly with KDE control settings OR this type of dynamic creating of one control module is going to be undertaken in the future. I know that just reporting a bug in yast, is met with a default WONTFIX due the impact on Gnome and the impact on both Enterprise products and Desktop/Server. THANK YOU - just for having a look. I still think that anything in Yast that doesn't work should be removed or hidden. Its not possible to create a working SAMBA Server via Yast and so many more apps so you probably have future plans that cant be discussed yet :-) -- 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=819515 https://bugzilla.novell.com/show_bug.cgi?id=819515#c Steffen Winterfeldt changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |mvidner@suse.com -- 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=819515 https://bugzilla.novell.com/show_bug.cgi?id=819515#c Scott Couston changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Non NFS V4 Mounts Stall the |Non NFS V4 AND NFSV4 Mounts |Boot Process for Minutes |Stall the Boot Process for |upon Minutes Until Huge |Minutes [TWENTY MINS ON |Value Time-outs |X_64 QUAD CORE] Until | |Time-Out -- 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=819515 https://bugzilla.novell.com/show_bug.cgi?id=819515#c10 Scott Couston changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Version|Final |Milestone 2 Component|YaST2 |Kernel AssignedTo|mvidner@suse.com |kernel-maintainers@forge.pr | |ovo.novell.com Product|openSUSE 12.2 |openSUSE 12.3 QAContact|jsrain@suse.com |qa-bugs@suse.de Summary|Non NFS V4 AND NFSV4 Mounts |Non NFS V4 AND NFSV4 Mounts |Stall the Boot Process for |Stall the Boot Process for |Minutes [TWENTY MINS ON |Minutes [TWENTY MINS ON |X_64 QUAD CORE] Until |X_64 QUAD CORE] Until |Time-Out |Time-Out can cannot | |dynamical mount or dismount | |NFS drives. Currently we | |have to boot each PC in the | |right Order to gain access | |to any NFS service Target Milestone|--- |RC 1 Severity|Normal |Major --- Comment #10 from Scott Couston 2013-08-16 10:11:44 EST --- I think the only way to fix this is to make changes to the Kernel as detailed above. This bug has been present since 10.2 and has been bug reported by myself for each and every version sine 10.2 the bug is closed as either INVALID/WONTFIX or has been left unassigned as NEW. Network services are a huge part of our product and still we cannot achieve a kernel bases continual dynamic check for server/client relationships and changes. Please put me out of my misery by either assigning this problem with a high priority for a fix in the next version 13.n or tell me that this is never going to be fixed as Netware File Servers can achieve network drives in Enterprise Suse Linux or any other impediment Can you please commit one way or another because 'indifference' is the only word that never belongs in software development. Please assign the your correct value for the 'Importance' field below -- 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=819515 https://bugzilla.novell.com/show_bug.cgi?id=819515#c12 --- Comment #12 from Scott Couston 2013-08-20 10:24:52 EST --- (In reply to comment #11)

Neil has already given you several solutions to the problem. We're not going to rewrite NFS in the kernel in a way that violates the spec because you don't want to use them.

Your reports get closed as WONTFIX because you don't accept the reasons we give for why a particular issue isn't a code problem and then expect us to develop based on your personal requirements.

For example, if you want YaST issues fixed that the YaST developers don't have time for or don't agree with, write the code yourself and submit it. openSUSE is the community project. Support is best-effort and development is driven by people working on the things they want to work on.

Thank you Jeff. Agree No Contest from me personally. Understand complexity of limited resources and funding. Disappointed from a product Open Suse point of view that our Product Fails in this regard. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=819515 Jiri Slaby changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED CC| |jslaby@suse.com Resolution|--- |WONTFIX --- Comment #15 from Jiri Slaby --- If you want any new functionality beyond what is implemented, feel free to send patches. This was already clsoed as wontfix and we have not changed our minds with respect to this. If you by a chance encoded a new report in the last comment and I overlooked that, open a new bug for it. -- You are receiving this mail because: You are on the CC list for the bug.