[Bug 649871] New: nfs mount failure during autoyast tftpboot
https://bugzilla.novell.com/show_bug.cgi?id=649871 https://bugzilla.novell.com/show_bug.cgi?id=649871#c0 Summary: nfs mount failure during autoyast tftpboot Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: beensen@nld.ds.mpg.de QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.41 Safari/534.7 We want to perform an autoyast auto-install via tftpboot/pxelinux from an AIX (IBM AIX 5.3 TL5 SP3 & HACMP 5.2) server. During boot, the client fails to mount the nfs-directory to get the SuSE packages. This is the error: <snip> Unable to create repository from URL 'nfs://192.168.216.12/path/to/root'. Details: Failed to mount 192.168.216.12:/path/to/root on /var/adm/mount/AP_0x00000001: Mounting media failed (mount.nfs: Remote I/O Error) <snap> I tried to switch to the console on ALT-F2 and issued the manual mount-command # mount -tnfs 192.168.216.12:/exports/ /mnt -v mount.nfs: timeout set for <date> mount.nfs: trying text-based options 'vers=4,addr=192.168.216.12,clientaddr=192.168.216.161' mount.nfs: mount(2): Remote I/O error mount.nfs: Remote I/O error Then I tried to mount with NFS version 3 and got # mount -tnfs 192.168.216.12:/exports/ /mnt -overs=3 -v mount.nfs: timeout set for <date> /usr/sbin/start-statd: line 8: /etc/sysconfig/nfs: No such file or directory mount.nfs: rpc.statd ist not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. mount.nfs: an incorrect mount option was specified Mounting from an already installed machine in the same network works without problems. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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=649871 https://bugzilla.novell.com/show_bug.cgi?id=649871#c Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffm@novell.com AssignedTo|kernel-maintainers@forge.pr |sjayaraman@novell.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=649871 https://bugzilla.novell.com/show_bug.cgi?id=649871#c1 Suresh Jayaraman <sjayaraman@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |nfbrown@novell.com --- Comment #1 from Suresh Jayaraman <sjayaraman@novell.com> 2010-11-25 12:11:34 UTC --- Thanks for the bug report. The first error you saw might be related to the fact the recent mount.nfs defaulted to version 4 since nfs-kernel-server >= 1.2.1 IIRC. While you can workaround this by using "vers=3" option as you did, leaving NFSv4 as default might possibly break existing setups (Ccing Neil Brown, nfs-utils maintainer for SUSE) for further opinion/comments. Does using the mount option 'nolock' help? The 'nolock' mount option is generally recommended particularly when the export is /var (or /usr) as they contain files used by the NLM implementation. -- 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=649871 https://bugzilla.novell.com/show_bug.cgi?id=649871#c Suresh Jayaraman <sjayaraman@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |beensen@nld.ds.mpg.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=649871 https://bugzilla.novell.com/show_bug.cgi?id=649871#c2 --- Comment #2 from Yorck-Fabian Beensen <beensen@nld.ds.mpg.de> 2010-11-26 10:31:59 UTC ---
Does using the mount option 'nolock' help? The 'nolock' mount option is generally recommended particularly when the export is /var (or /usr) as they contain files used by the NLM implementation.
Yes, using the 'nolock' mount option, we can mount the directory. However, we want to perform an automatic installation. Is there any way to pass the options "vers=3,nolock" to the installer automatically? The options would probably have to be communicated via kernel-options? Cheers, Matthias -- 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=649871 https://bugzilla.novell.com/show_bug.cgi?id=649871#c3 --- Comment #3 from Suresh Jayaraman <sjayaraman@novell.com> 2010-11-30 08:28:39 UTC --- (In reply to comment #2)
Does using the mount option 'nolock' help? The 'nolock' mount option is generally recommended particularly when the export is /var (or /usr) as they contain files used by the NLM implementation.
Yes, using the 'nolock' mount option, we can mount the directory.
However, we want to perform an automatic installation. Is there any way to pass the options "vers=3,nolock" to the installer automatically? The options would probably have to be communicated via kernel-options?
I'm not sure whether it is possible to pass nfs options to auto installer. But as an alternative, you could try using NFSv4 itself instead of NFSv3. NFSv4 configuration is simple: - On the Server, edit /etc/exports and add "fsid=0" to the options for e.g. /Engineering 192.168.1.15(rw,sync,fsid=0) - #exportsfs -r (to re-export all dirs) - While using autoyast on the client skip mentioning the exported directory for e.g. If you had used something like: nfs://192.168.216.12/path/to/root to use NFSv4, just say: nfs://192.168.216.12 Note: * NFSv4 has a concept of a root of the overall exported filesystem. The export point exported with fsid=0 will be used as this root. See man nfs for more information -- 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=649871 https://bugzilla.novell.com/show_bug.cgi?id=649871#c4 --- Comment #4 from Suresh Jayaraman <sjayaraman@novell.com> 2010-12-07 09:03:59 UTC --- Ping! -- 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=649871 https://bugzilla.novell.com/show_bug.cgi?id=649871#c5 --- Comment #5 from Yorck-Fabian Beensen <beensen@nld.ds.mpg.de> 2010-12-07 09:48:35 UTC --- Hi, thanks for the suggestion, but we would like to stick to NFSv3 on our AIX server. We currently circumvent the problem by serving the autoyast-file via http. Cheers, Matthias -- 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=649871 https://bugzilla.novell.com/show_bug.cgi?id=649871#c6 --- Comment #6 from Suresh Jayaraman <sjayaraman@novell.com> 2010-12-14 08:05:02 UTC --- Looking more closely, it appears that the problem here is Old AIX server returning "EREMOTEIO" instead of "ENOENT" error. Linux clients fallback to NFSv3 in case of ENOENT error as expected. I verified this in a 11.3 Server Vs 11.3 client setup and there were no errors observed. AFAIK, there is no way to pass NFS mount options via Autoyast. I think apart from getting AIX server fixed, the other option would be to make linux client handle EREMOTEIO error from the legacy AIX servers. I have built the nfs-utils/nfs-kernel-server packages with the above mentioned fix and made it available here: http://www.suse.com/~sjayaraman/test-pkgs/ Could you please test this package and see whether the error go away? -- 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=649871 https://bugzilla.novell.com/show_bug.cgi?id=649871#c7 --- Comment #7 from Suresh Jayaraman <sjayaraman@novell.com> 2011-01-13 04:42:43 UTC --- Ping! -- 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=649871 https://bugzilla.novell.com/show_bug.cgi?id=649871#c8 --- Comment #8 from Suresh Jayaraman <sjayaraman@novell.com> 2011-02-02 04:47:20 UTC --- Ping! Could you test the package and see whether it resolves the issue for you? -- 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=649871 https://bugzilla.novell.com/show_bug.cgi?id=649871#c9 Suresh Jayaraman <sjayaraman@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |CLOSED InfoProvider|beensen@nld.ds.mpg.de | Resolution| |NORESPONSE --- Comment #9 from Suresh Jayaraman <sjayaraman@novell.com> 2011-02-08 10:52:02 UTC --- I'll close this as NO RESPONSE. There is no way for me to be sure whether the Linux workaround for patch fixes this problem or not and in any case legacy AIX servers have to be fixed to return "ENOENT" instead of "EREMOTEIO". So, I would rather not commit this fix. -- 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.
participants (1)
-
bugzilla_noreply＠novell.com