https://bugzilla.novell.com/show_bug.cgi?id=815738
https://bugzilla.novell.com/show_bug.cgi?id=815738#c0
Summary: mkinitrd fails to create working system for nfs boot Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: pizza@glidos.net QAContact: jsrain@suse.com Found By: --- Blocker: ---
Issuing the command: mkinitrd -k vnlinuz-3.7.10-1.1-desktop -i initrdnfs -d /dev/nfs -f nfs -D eth0 -B
results in a initrdnfs which fails on boot at the stage of mounting the root file system, with error report "mount.nfs: Protocol not supported".
I believe it is because nfs_v3 and nfs_v4 have been made separate kernal modules. Applying some wild guess work, I was able to fix the problem by adding " nfsv3" to the end of the line "#%modules: nfs" in file /lib/mkinitrd/scripts/boot-nfs.sh
https://bugzilla.novell.com/show_bug.cgi?id=815738
https://bugzilla.novell.com/show_bug.cgi?id=815738#c
Xiaolong Li xlli@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |xlli@suse.com AssignedTo|bnc-team-screening@forge.pr |mmarek@suse.com |ovo.novell.com |
https://bugzilla.novell.com/show_bug.cgi?id=815738
https://bugzilla.novell.com/show_bug.cgi?id=815738#c1
Olaf Hering ohering@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |nfbrown@suse.com
--- Comment #1 from Olaf Hering ohering@suse.com 2013-08-02 16:32:16 CEST --- Neil,
is it safe to include nfsv2,nfsv3,nfsv4 into initrd and load them all in advance in initrd?
I have not tested a nfsv4 share, what it takes to drive such a share. Does nfsv4 have extra dependencies? I see nfs-layouttype4-1.ko, is that module required as well? Can the setup scripts easily detect an nfsv4 share and create the required setup in initrd?
Can the server easily change its version across client reboots (v3 becomes v4) and could the unmodified client cope with such a change?
https://bugzilla.novell.com/show_bug.cgi?id=815738
https://bugzilla.novell.com/show_bug.cgi?id=815738#c2
Neil Brown nfbrown@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |nfbrown@suse.com InfoProvider|nfbrown@suse.com |
--- Comment #2 from Neil Brown nfbrown@suse.com 2013-08-05 07:09:29 UTC --- Yes, it is safe to include those 3 nfs modules. nfsv4 has fewer dependencies than v3 (e.g. locking is not an issue).
nfs-layouttype4-1.ko is for 'pNFS'. You don't need that in the initrd.
The NFS server will normally support all versions. However if it does stop supporting one, the client should cope.
There should be no difference in the initrd. Simply try to mount the appropriate directory from the appropriate server. mount.nfs will try various protocols until it works.
https://bugzilla.novell.com/show_bug.cgi?id=815738
https://bugzilla.novell.com/show_bug.cgi?id=815738#c3
Olaf Hering ohering@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |pizza@glidos.net
--- Comment #3 from Olaf Hering ohering@suse.com 2013-08-05 15:38:13 CEST --- I will submit this change to nfs-utils, its also required for 12.3 mount.nfs4 is probably needed, I did not test this part.
Paul, please re-test this change for /lib/mkinitrd/scripts/boot-nfs.sh
Index: mkinitrd-boot.sh =================================================================== --- mkinitrd-boot.sh (revision bbc170fc5de5dd1d808d5e9b785c0a54) +++ mkinitrd-boot.sh (working copy) @@ -1,7 +1,7 @@ #!/bin/bash #%stage: block -#%modules: nfs -#%programs: /sbin/mount.nfs +#%modules: nfsv2 nfsv3 nfsv4 +#%programs: mount.nfs mount.nfs4 #%if: "$rootfstype" = "nfs" -o "$need_nfs" # ##### Network FileSystem
https://bugzilla.novell.com/show_bug.cgi?id=815738
https://bugzilla.novell.com/show_bug.cgi?id=815738#c4
--- Comment #4 from Bernhard Wiedemann bwiedemann@suse.com 2013-08-05 20:00:29 CEST --- This is an autogenerated message for OBS integration: This bug (815738) was mentioned in https://build.opensuse.org/request/show/185979 Factory / nfs-utils
https://bugzilla.novell.com/show_bug.cgi?id=815738
https://bugzilla.novell.com/show_bug.cgi?id=815738#c5
Olaf Hering ohering@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fabian@ritter-vogt.de
--- Comment #5 from Olaf Hering ohering@suse.com 2013-08-08 10:34:36 CEST --- *** Bug 823671 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=823671
https://bugzilla.novell.com/show_bug.cgi?id=815738
https://bugzilla.novell.com/show_bug.cgi?id=815738#c6
Paul Gardiner pizza@glidos.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|pizza@glidos.net |
--- Comment #6 from Paul Gardiner pizza@glidos.net 2013-08-11 15:08:05 UTC --- (In reply to comment #3)
I will submit this change to nfs-utils, its also required for 12.3 mount.nfs4 is probably needed, I did not test this part.
Paul, please re-test this change for /lib/mkinitrd/scripts/boot-nfs.sh
Index: mkinitrd-boot.sh
--- mkinitrd-boot.sh (revision bbc170fc5de5dd1d808d5e9b785c0a54) +++ mkinitrd-boot.sh (working copy) @@ -1,7 +1,7 @@ #!/bin/bash #%stage: block -#%modules: nfs -#%programs: /sbin/mount.nfs +#%modules: nfsv2 nfsv3 nfsv4 +#%programs: mount.nfs mount.nfs4 #%if: "$rootfstype" = "nfs" -o "$need_nfs" # ##### Network FileSystem
Yes Olaf, that works just fine, thank you.
https://bugzilla.novell.com/show_bug.cgi?id=815738
https://bugzilla.novell.com/show_bug.cgi?id=815738#c7
Olaf Hering ohering@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mmarek@suse.com |nfbrown@suse.com
--- Comment #7 from Olaf Hering ohering@suse.com 2013-08-12 21:35:31 CEST --- The patch above should go into 12.3
https://bugzilla.novell.com/show_bug.cgi?id=815738
https://bugzilla.novell.com/show_bug.cgi?id=815738#c8
--- Comment #8 from Bernhard Wiedemann bwiedemann@suse.com 2013-08-14 04:00:09 CEST --- This is an autogenerated message for OBS integration: This bug (815738) was mentioned in https://build.opensuse.org/request/show/186986 Maintenance / https://build.opensuse.org/request/show/186987 Maintenance /
https://bugzilla.novell.com/show_bug.cgi?id=815738
https://bugzilla.novell.com/show_bug.cgi?id=815738#c9
--- Comment #9 from Swamp Workflow Management swamp@suse.de 2013-08-21 13:04:22 UTC --- openSUSE-RU-2013:1365-1: An update that has one recommended fix can now be installed.
Category: recommended (moderate) Bug References: 815738 CVE References: Sources used: openSUSE 12.3 (src): nfs-utils-1.2.7-2.14.1
https://bugzilla.novell.com/show_bug.cgi?id=815738
https://bugzilla.novell.com/show_bug.cgi?id=815738#c10
Patrick Feucht patrick.feucht@kabelbw.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |patrick.feucht@kabelbw.de
--- Comment #10 from Patrick Feucht patrick.feucht@kabelbw.de 2013-08-21 14:54:25 UTC --- *** Bug 834458 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=834458
https://bugzilla.novell.com/show_bug.cgi?id=815738
https://bugzilla.novell.com/show_bug.cgi?id=815738#c11
Neil Brown nfbrown@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #11 from Neil Brown nfbrown@suse.com 2013-09-02 02:56:14 UTC --- This is in 11.3 and Factory, so resolving as Fixed.
-
bugzilla_noreply＠novell.com