Skip to contentSkip to conversation

NFS problem after upgrade from 2.6.32 to 2.6.3[3-7]

DISCUSSION Henrik Grindal Bakken 2 participants 3 messages Nov 18, 2010 – Nov 19, 2010

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

Hi. I'm running a (home-brew) linux distro on a powerpc, which exports a yaffs2 filesystem via nfs to some arm-linuxes.

This has worked fine with kernels up to and including 2.6.32, but when trying to upgrade further, we've been running into problems.

I didn't try 2.6.3[345] myself, but the reports were that nfs somehow didn't work. I'm trying 2.6.37-rc2 now after trying 2.6.36 earlier, and I get the following problem:

$ grep -v '^#' /etc/netconfig 
udp        tpi_clts      v     inet     udp     -       -
udp6       tpi_clts      v     inet6    udp     -       -
local      tpi_cots_ord  -     loopback  -      -       -
$ rpcbind
$ rpc.mountd --no-tcp
$ rpc.nfsd -H ppc -N 4 -T
svc: failed to register nfsdv2 RPC service (errno 111).
nfsd: last server has exited, flushing export cache
rpc.nfsd: writing fd to kernel failed: errno 111 (Connection refused)
rpc.nfsd: unable to set any sockets for nfsd

I've tried to google the error message, to no avail. The only hits I get are from commit messages.

I'm running nfs-utils-1.2.3, configured with

./configure --with-tcp-wrappers=no --disable-nfsv4 --enable-uuid=no \
    --disable-gss --enable-mount=no

NFS-related kernel configs:
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
CONFIG_NFS_V4=y
# CONFIG_NFS_V4_1 is not set
CONFIG_ROOT_NFS=y
CONFIG_NFS_USE_LEGACY_DNS=y
CONFIG_NFSD=y
CONFIG_NFSD_DEPRECATED=y
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not set
CONFIG_NFSD_V4=y
CONFIG_NFS_COMMON=y

Does anyone have any pointers?

Signature · 3 lines
Henrik Grindal Bakken <hgb-6miFZF/[email protected]>
PGP ID: 8D436E52
Fingerprint: 131D 9590 F0CF 47EF 7963  02AF 9236 D25A 8D43 6E52
#1 lore raw
Quoted 23 lines · Henrik Grindal Bakken

Hi. I'm running a (home-brew) linux distro on a powerpc, which exports a yaffs2 filesystem via nfs to some arm-linuxes.

This has worked fine with kernels up to and including 2.6.32, but when trying to upgrade further, we've been running into problems.

I didn't try 2.6.3[345] myself, but the reports were that nfs somehow didn't work. I'm trying 2.6.37-rc2 now after trying 2.6.36 earlier, and I get the following problem:

$ grep -v '^#' /etc/netconfig 
udp        tpi_clts      v     inet     udp     -       -
udp6       tpi_clts      v     inet6    udp     -       -
local      tpi_cots_ord  -     loopback  -      -       -
$ rpcbind
$ rpc.mountd --no-tcp
$ rpc.nfsd -H ppc -N 4 -T
svc: failed to register nfsdv2 RPC service (errno 111).
nfsd: last server has exited, flushing export cache
rpc.nfsd: writing fd to kernel failed: errno 111 (Connection refused)
rpc.nfsd: unable to set any sockets for nfsd
Quoted 2 lines

I've tried to google the error message, to no avail. The only hits I get are from commit messages.

One thing to note: the kernel uses TCP when performing rpcbind registration upcalls. You might try adding back the TCP entries in /etc/netconfig to cause rpcbind to create TCP listeners.

Quoted 31 lines

I'm running nfs-utils-1.2.3, configured with

./configure --with-tcp-wrappers=no --disable-nfsv4 --enable-uuid=no \
   --disable-gss --enable-mount=no

NFS-related kernel configs:
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
CONFIG_NFS_V4=y
# CONFIG_NFS_V4_1 is not set
CONFIG_ROOT_NFS=y
CONFIG_NFS_USE_LEGACY_DNS=y
CONFIG_NFSD=y
CONFIG_NFSD_DEPRECATED=y
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not set
CONFIG_NFSD_V4=y
CONFIG_NFS_COMMON=y

Does anyone have any pointers?

Signature · 8 lines
Henrik Grindal Bakken <[email protected]>
PGP ID: 8D436E52
Fingerprint: 131D 9590 F0CF 47EF 7963  02AF 9236 D25A 8D43 6E52

--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Signature · 2 lines
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
#2 lore raw
Quoted 8 lines · Chuck Lever
Quoted 2 lines · Henrik Grindal Bakken

I've tried to google the error message, to no avail. The only hits I get are from commit messages.

One thing to note: the kernel uses TCP when performing rpcbind registration upcalls. You might try adding back the TCP entries in /etc/netconfig to cause rpcbind to create TCP listeners.

That solved it! Thanks. I was convinced I had tried that, but apparently I hadn't.

Signature · 3 lines
Henrik Grindal Bakken <hgb-6miFZF/[email protected]>
PGP ID: 8D436E52
Fingerprint: 131D 9590 F0CF 47EF 7963  02AF 9236 D25A 8D43 6E52