Casper doesn't properly support NFSOPTS

Bug #1844761 reported by Alkis Georgopoulos
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
casper (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

From https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt:
nfsroot=[<server-ip>:]<root-dir>[,<nfs-options>]

NFSOPTS are properly supported by initramfs-tools/scripts/nfs:
if [ "${NFSROOT#*,}" != "${NFSROOT}" ]; then
    NFSOPTS="-o ${NFSROOT#*,}"
fi

But casper doesn't support them properly like this.
Casper assumes that the scripts/nfs code has already ran and set NFSOPTS, which it didn't.
So the only way to set NFSOPTS with casper is to actually pass NFSOPTS=xxx in the kernel cmdline; the kernel itself then passes this as an init parameter.

This behavior is wrong and undocumented, NFSOPTS isn't a kernel parameter but an internal variable of initramfs-tools/scripts/nfs, which isn't set when casper runs, and casper needs to set it by doing an "if" like the one above ^.

Tags: patch
Revision history for this message
Alkis Georgopoulos (alkisg) wrote :
tags: added: patch
Changed in casper (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.