strange nfs problem, need nfs guru
Gene Heskett
gheskett at wdtv.com
Thu Aug 21 09:45:09 UTC 2014
On Thursday 21 August 2014 03:21:23 Tom H did opine
And Gene did reply:
> On Wed, Aug 20, 2014 at 3:26 PM, Gene Heskett <gheskett at wdtv.com> wrote:
> > On Wednesday 20 August 2014 08:15:22 Tom H did opine
> >
> > And Gene did reply:
> >> On Wed, Aug 20, 2014 at 7:23 AM, Gene Heskett <gheskett at wdtv.com>
wrote:
> >>> * Stopping NFS kernel daemon
> >>> [ OK ]
> >>> * Unexporting directories for NFS kernel daemon...
> >>> [ OK ]
> >>> * Not starting NFS kernel daemon: no support in current kernel.
> >>
> >> grep nfs /proc/filesystems
> >
> > gene at coyote:/var/log$ grep nfs /proc/filesystems
> > nodev nfs
> > nodev nfs4
> > nodev nfsd
>
> Your kernel has nfs support so OK.
>
> I could've sworn that nfs-kernel-server was now being started via a
> native upstart job but I must've been confusing it with rpcbind!
>
> Anyway, it looks like your kernel's failing this test in
> "/etc/init.d/nfs-kernel-server":
>
> # See if our running kernel supports the NFS kernel
> server if ! grep -E -qs "[[:space:]]nfsd\$" /proc/filesystems; then
> log_warning_msg "Not starting $DESC: no support in current kernel."
> exit 0
> fi
>
> 1) Add "-x" to the shebang and see if the more verbose output explains
> why the test's failing.
>
> 2) Does nfs start up if you delete "\$" from "[[:space:]]nfsd\$"?
>
Where is this? It doesn't exist in the /etc/init.d script
> 3) Does nfs start up if you use a distro kernel rather than a
> self-built one? (Ubuntu builds a lot of NFS as modules.)
>
> >> cat /etc/default/{nfs-common,nfs-kernel-server}
> >
> > gene at coyote:/var/log$ cat /etc/default/{nfs-common,nfs-kernel-server}
> > ...
>
> You have the default settings so OK.
>
> >> The syntax of "/etc/exports" is strict. I've never seen or used a
> >> trailing "/" so I'd delete it if I were you, although this might be
> >> a non-issue.
> >
> > I did have a /24 there, took it out, no diff. Exact same error
> > message.
>
> I meant the trailing slash in "/home/gene/" but I've just added it to
> an export of mine and it was OK.
All of my exports on the other machines have that /ip xx.xx.xx.xx/24
appended, works fine.
I just put the -x in the shebang, and I'll start the trace copy after the
shutdown:
eq 0 ]
+ echo [ OK ]
[ OK ]
+ return 0
+ mountpoint -q /proc/fs/nfsd
+ exit 0
+ sleep 1
+ /etc/init.d/nfs-kernel-server start
+ DESC=NFS kernel daemon
+ PREFIX=/usr
+ [ -x /usr/sbin/rpc.nfsd ]
+ [ -x /usr/sbin/rpc.mountd ]
+ [ -x /usr/sbin/exportfs ]
+ DEFAULTFILE=/etc/default/nfs-kernel-server
+ RPCNFSDCOUNT=8
+ RPCNFSDPRIORITY=0
+ RPCMOUNTDOPTS=
+ NEED_SVCGSSD=no
+ RPCSVCGSSDOPTS=
+ PROCNFSD_MOUNTPOINT=/proc/fs/nfsd
+ [ -f /etc/default/nfs-kernel-server ]
+ . /etc/default/nfs-kernel-server
+ RPCNFSDCOUNT=8
+ RPCNFSDPRIORITY=0
+ RPCMOUNTDOPTS=--manage-gids
+ NEED_SVCGSSD=no
+ RPCSVCGSSDOPTS=
+ . /lib/lsb/init-functions
+ FANCYTTY=
+ [ -e /etc/lsb-base-logging.sh ]
+ . /etc/lsb-base-logging.sh
+ [ -f /etc/exports ]
+ do_modprobe nfsd
+ [ -x /sbin/modprobe -a -f /proc/modules ]
+ modprobe -q nfsd
+ [ -f /proc/kallsyms ]
+ grep -qE nfsd_serv /proc/kallsyms
+ log_warning_msg Not starting NFS kernel daemon: no support in current
kernel.
+ log_use_usplash
+ [ n = y ]
+ type usplash_write
+ log_use_fancy_output
+ TPUT=/usr/bin/tput
+ EXPR=/usr/bin/expr
+ [ -t 1 ]
+ [ xxterm != x ]
+ [ xxterm != xdumb ]
+ [ -x /usr/bin/tput ]
+ [ -x /usr/bin/expr ]
+ /usr/bin/tput hpa 60
+ /usr/bin/tput setaf 1
+ [ -z ]
+ FANCYTTY=1
+ true
+ /usr/bin/tput setaf 3
+ YELLOW=
+ /usr/bin/tput op
+ NORMAL=
+ echo * Not starting NFS kernel daemon: no support in current kernel.
* Not starting NFS kernel daemon: no support in current kernel.
+ exit 0
+ exit 0
And, this is a freshly built and rebooted to 3.16.0 kernel. There is not
an nfsd.ko in the /lib/modules/3.16.0 tree because its all built in.
From the .config that built this kernel:
gene at coyote:/usr/src/linux-3.16.0$ grep NFS .config
CONFIG_KERNFS=y
CONFIG_NFS_FS=y
# CONFIG_NFS_V2 is not set
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
# CONFIG_NFS_SWAP is not set
CONFIG_NFS_V4_1=y
CONFIG_NFS_V4_2=y
CONFIG_PNFS_FILE_LAYOUT=y
CONFIG_PNFS_BLOCK=m
CONFIG_PNFS_OBJLAYOUT=m
CONFIG_NFS_V4_1_IMPLEMENTATION_ID_DOMAIN="kernel.org"
# CONFIG_NFS_V4_1_MIGRATION is not set
# 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_NFSD_FAULT_INJECTION is not set
CONFIG_NFS_ACL_SUPPORT=y
CONFIG_NFS_COMMON=y
So everything s/b builtin.
On the machines where the exports work, nfsd_serv does have a grep hit out
of /proc/kallsyms.
On this machine it does not exist. doing a modprobe for it is an empty
return. Because its builtin, or supposed to be, it doesn't show in an
lsmod, but I was under the impression that kallsyms would contain its name
and offset address if it existed.
So the failure is legit. I'll go back over my make xconfig again. My
"makeit" script is supposed to fail, leaving the failure on screen if
something does not build. Back later after I check it again.
As for distro kernels here on this machine, there are none, or only one
'distro' but the distro is available, based on 10.04.4 LTS, from the
linuxcnc.org site. This whole distro for running linuxcnc has a frozen
kernel because of the extremely invasive patches needed to get real time
performance, using the RTAI patch kit. Default kernel is a 2.6.32-122-
rtai. For smaller machines, it is not SMP nor PAE configured. Runs
great on a machine with a single 2G ram in it, on an atom cpu.
Its a terminally ill dog kernel on a phenom with 8Gb of dram, using as
much as 3Gb of swap in a 24 hour uptime because it cannot see the full
memory in this machine. I am happy running the lcnc as a simulator here
as there is not any dangerous machinery waiting for commands on the
partport.
Thanks
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS
More information about the ubuntu-users
mailing list