kernel-2.6.10-1.741_FC3 has broken nfs

Ian Laurie iml at zip.com.au
Sun Jan 30 06:12:54 UTC 2005


On Sat, 29 Jan 2005 23:06:53 -0600, Jonathan Berry wrote:
> On Sun, 30 Jan 2005 00:08:33 +0000, Ian Laurie <iml at zip.com.au>
> wrote:
>> The latest kernel seems to have broken nfs, previous kernel was
>> OK.
>>
>> I'm getting this in the log file:
>>
>> Jan 30 10:37:25 zaurak modprobe: WARNING: Error inserting lockd
>> (/lib/modules/2.6.10-1.741_FC3/kernel/fs/lockd/lockd.ko): Unknown
>> symbol in module, or unknown parameter (see dmesg)
>> Jan 30 10:37:25 zaurak modprobe: WARNING: Error inserting lockd
>> (/lib/modules/2.6.10-1.741_FC3/kernel/fs/lockd/lockd.ko): Unknown
>> symbol in module, or unknown parameter (see dmesg)
>> Jan 30 10:37:25 zaurak modprobe: FATAL: Error inserting nfsd
>> (/lib/modules/2.6.10-1.741_FC3/kernel/fs/nfsd/nfsd.ko): Unknown
>> symbol in module, or unknown parameter (see dmesg)
>> Jan 30 10:37:25 zaurak modprobe: FATAL: Error running install
>> command for nfsd
>> Jan 30 10:37:25 zaurak kernel: lockd: Unknown parameter `'
>> Jan 30 10:37:25 zaurak kernel: lockd: Unknown parameter `'
>> Jan 30 10:37:25 zaurak kernel: nfsd: Unknown symbol lockd_down
>> Jan 30 10:37:25 zaurak kernel: nfsd: Unknown symbol lockd_up
>> Jan 30 10:37:25 zaurak kernel: nfsd: Unknown symbol nlmsvc_ops
>> Jan 30 10:37:25 zaurak nfsd[25698]: nfssvc: No such device
>> Jan 30 10:37:25 zaurak nfs: rpc.nfsd startup failed
>> Jan 30 10:37:26 zaurak nfs: rpc.mountd startup succeeded
>>
>> Anyone got any ideas about this?
>>
>> All dmesg says is:
>>
>> lockd: Unknown parameter `'
>>
>> This has me baffled.  I can get nfs working by booting the
>> previous kernel
>> though.
>>
>> Ian
>
> I've seen this recently with the nvidia module.  The fix was to edit
> /etc/modprobe.conf and remove the trailing whitespace from the
> options
> line.  If you have been using system-config-network lately, whenever
> you save, it rewrites /etc/modprobe.conf and adds a space to the end
> of all options lines.  Obviously, some (all?) modules don't parse
> the
> options correctly if there is extra trailing whitespace (which seems
> like a bad situation).  Anyway, there is a bugzilla entry on the
> system-config-network:
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=146291
>
> Jonathan

Jonathan,

Thank you !!  This did indeed fix the problem.  There were about 4 trailing
spaces.  Weird how the other kernel worked though.

Seems to me the bug should be fixed in the parsing of the lines though.
It shouldn't matter if there are trailing spaces, that can easily be
done in an editor by mistake.  Fixing system-config-network will just
hide the bug in some cases.

Ian





More information about the users mailing list