On 2016/06/12 at 11:00, Dave Young wrote:
>>>> For nfs,
>>>> 1) if we specify "dracut_args --mount
"10.66.129.115:/export/nfs /test nfs defaults",
>>>> then "nfs.ko" will be added to initramfs only.
>>>> 2) if we specify "dracut_args --mount
"10.66.129.115:/export/nfs /test nfsv4 defaults",
>>>> then both "nfs.ko" and "nfsv4.ko" will be added.
>>> Further investigation shows that this can't work, the reason why nfsv4.ko
is added is because
>>> in 90kernel-modules/module-setup.sh installkernel(), we have:
>>> for i in $(host_fs_all); do
>>> hostonly='' instmods $i
>>> done
>>>
>>> So nfsv4.ko which is got from the fstype is added, but actually the mount
will fail due to the invalid
>>> "nfsv4" specified in "--mount"(the right one should be
"nfs4").
>> Seems we are still not clear about the problem, shouldn't it been mapped
from
>> nfs4 -> nfsv4.ko automaticlly?
> Unfortunately, the current implementation does no mapping about this.
> Maybe we could throw a patch on this to let "nfs4" mapping to
"nfsv4" for
> instmods.
From nfs manpage nfs4 fstype is deprecated, -o vers=4 is prefered
instead. In case without -o vers, 4 will be tried first, then 3, then 2.
For this patch, we use dracut's "--mount", which requires a <filesystem
type> mandatorily, so this should not be an issue.
Regards,
Xunlei
So for nfs, maybe the right way is including all the kernel modules
Thanks
Dave