[Lucid] NFS kernel server doesn't work anymore with 2.6.32

Bug #493145 reported by Philip Muškovac
38
This bug affects 6 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Andy Whitcroft
nfs-utils (Debian)
Fix Released
Unknown
nfs-utils (Ubuntu)
Fix Released
Medium
Andy Whitcroft

Bug Description

$ sudo service nfs-kernel-server start
 * Not starting NFS kernel daemon: no support in current kernel.

The same happens with 2.6.32-020632-generic

Using 2.6.31-16-server in Lucid works fine.

ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: yofel 4054 F.... pulseaudio
                      yofel 4064 F.... kmix
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfe220000 irq 17'
   Mixer name : 'Analog Devices AD1984'
   Components : 'HDA:11d41984,17aa20bb,00100400'
   Controls : 29
   Simple ctrls : 18
Date: Sun Dec 6 14:01:24 2009
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=b46ef0e3-f5b1-4a56-b9c2-0e19ef7fc823
MachineType: LENOVO 89196VG
NonfreeKernelModules: nvidia
Package: linux-image-2.6.32-6-server 2.6.32-6.8
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-6-server root=UUID=30e41245-f7b8-4e7b-aa38-a5b3aa2cc044 ro crashkernel=384M-2G:64M,2G-:128M security=apparmor vga=0x0368
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-6.8-server
Regression: Yes
RelatedPackageVersions: linux-firmware 1.27
Reproducible: Yes
SourcePackage: linux
Tags: lucid regression-proposed
TestedUpstream: Yes
Uname: Linux 2.6.32-6-server x86_64
dmi.bios.date: 05/08/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 7KETC8WW (2.28 )
dmi.board.name: 89196VG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7KETC8WW(2.28):bd05/08/2009:svnLENOVO:pn89196VG:pvrThinkPadR61:rvnLENOVO:rn89196VG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 89196VG
dmi.product.version: ThinkPad R61
dmi.sys.vendor: LENOVO

Revision history for this message
Philip Muškovac (yofel) wrote :
tags: added: regression-potential
removed: regression-proposed
description: updated
Philip Muškovac (yofel)
description: updated
Andy Whitcroft (apw)
tags: added: kernel-lucid
Revision history for this message
Andy Whitcroft (apw) wrote :

I believe that this is a false negative detect of kernel support of NFS. The current scripts look for specific symbol prefixes to indicate that the kernel now has an nfsd having attempted to load the nfsd module. It seem that those symbols are no longer there leading to this false detection of no kernel support.

Added a task for nfs-kernel-server as this is a userspace detection issue.

Andy Whitcroft (apw)
Changed in nfs-utils (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → Andy Whitcroft (apw)
Changed in linux (Ubuntu):
assignee: nobody → Andy Whitcroft (apw)
importance: Undecided → Medium
status: New → Invalid
Revision history for this message
Andy Whitcroft (apw) wrote :

The attached debdiff seems to allow the scripting to correctly detect a working nfs server in the kernel.

Changed in nfs-utils (Ubuntu):
status: Triaged → In Progress
Revision history for this message
Philip Muškovac (yofel) wrote :

With your patch NFS works fine again, thanks!

Revision history for this message
Andy Whitcroft (apw) wrote :

Having had the patch reviewed, it was suggested that given the age of the nfsd_serv symbol we could simply check that alone. Based on that attached is an updated patch with that simplification.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package nfs-utils - 1:1.2.0-4ubuntu2

---------------
nfs-utils (1:1.2.0-4ubuntu2) lucid; urgency=low

  * debian/nfs-kernel-server.init: 2.6.32 kernels no longer export the
    same symbols. Switch symbol check to nfsd_serv which has been present
    since 2005. LP: #493145.
 -- Andy Whitcroft <email address hidden> Mon, 07 Dec 2009 16:56:56 +0000

Changed in nfs-utils (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Ben Hutchings (benh-debian) wrote :

I substituted a much cleaner test in Debian (see the linked bug report) and suggest you take that change.

Revision history for this message
Steve Langasek (vorlon) wrote :

As near as I can tell, the Debian fix is incorrect because /sys/module/nfsd is only available if nfsd is built as a module. Anyone who has the code built into their kernel will not have this directory.

Changed in nfs-utils (Debian):
status: Unknown → Fix Released
Revision history for this message
Richard Huddleston (rhuddusa) wrote :

I'm unclear as to what fix released as of 2009-12-30 means in this case

I'm seeing this issue in Karmic with 2.6.32 kernel

uname --all
Linux box05 2.6.32-02063204-generic #02063204 SMP Tue Jan 19 10:10:25 UTC 2010 x86_64 GNU/Linux

dpkg -l | grep nfs
ii libnfsidmap2 0.21-2 An nfs idmapping library
ii nfs-common 1:1.2.0-2ubuntu8 NFS support files common to client and serve
ii nfs-kernel-server 1:1.2.0-2ubuntu8 support for NFS kernel server

lsmod | grep nfs
nfsd 302808 2
exportfs 4243 1 nfsd
nfs 313682 0
lockd 73309 2 nfsd,nfs
nfs_acl 2771 2 nfsd,nfs
auth_rpcgss 44276 2 nfsd,nfs
sunrpc 225181 6 nfsd,nfs,lockd,nfs_acl,auth_rpcgss

grep -qE 'init_nf(sd| )' /proc/kallsyms
returns nothing

Revision history for this message
Philip Muškovac (yofel) wrote :

@Richard: Fix Released means that this was fixed in the development release (currently Lucid Lynx) as that's where 2.6.32 is used. I fear you'll have to backport the lucid nfs-utils to karmic if you want to use nfs-kernel-server in karmic with 2.6.32.

Revision history for this message
Philip Muškovac (yofel) wrote :

@Richard: or you can just patch the karmic version to use the lucid check:

                if [ -f /proc/kallsyms ] && ! grep -qE ' nfsd_serv ' /proc/kallsyms; then

Revision history for this message
Richard Huddleston (rhuddusa) wrote :

@Philip

I went with the patch you gave ... only i had to slightly modify it

rhuddusa@box05:~$ grep -E ' nfsd_serv ' /proc/kallsyms
rhuddusa@box05:~$ grep -E ' nfsd_serv' /proc/kallsyms
ffffffffa0cfc488 b nfsd_serv [nfsd]

i removed the space at the end of the quote. i don't know if this was the correct thing to do but the nfs-kernel-server service starts now :)

Your patch (with my change) works on Karmic with kernels
2.6.32-02063205-generic
2.6.31-17-server
2.6.31-17-generic

Revision history for this message
Richard Huddleston (rhuddusa) wrote :

@Philip

My bad, white space issue, I looked at and saw the correct white space

http://launchpadlibrarian.net/36599969/nfs-kernel-server-2.6.32-kernel-detect-v2

Revision history for this message
Bart Verwilst (verwilst) wrote :

I'm still seeing this on a Lucid install with a custom 2.6.34 kernel which has nfsd loaded as a module. The debian bugreport mentions checking for /proc/fs/nfs/exports, which i indeed have. There is no mention of nfsd_serv in /proc/kallsyms though..

Revision history for this message
Juan Simón (simonbcn) wrote :

Same error in Lucid 10.04 32 bits with kernel 2.6.36.2 and this NFS config:

$ grep -i nfs /boot/config-2.6.36.2-20101226
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
# CONFIG_NFS_V4_1 is not set
CONFIG_NFS_FSCACHE=y
# CONFIG_NFS_USE_LEGACY_DNS is not set
CONFIG_NFS_USE_KERNEL_DNS=y
CONFIG_NFSD=y
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_NFS_ACL_SUPPORT=y
CONFIG_NFS_COMMON=y
CONFIG_NCPFS_NFS_NS=y

Revision history for this message
Juan Simón (simonbcn) wrote :

I have updated packages: nfs-kernel-server and nfs-common to Maverick versions and now it works.
Why Lucid isn't updated if it's a LTS version!? :-(

Revision history for this message
Philip Muškovac (yofel) wrote :

@Simon: My bug was fixed and it works perfectly fine here, also you're using kernel 2.6.36.2 which is *not* a kernel supported under LTS conditions, Lucid LTS only supports 2.6.32. If you want to use a newer kernel then you'll have to make sure everything else is up-to-date yourself.

Anyway, since this bug is fix released, please file a new bug for your issue if you think it's neccessary.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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