From: Henrik Grindal Bakken <hgb-6miFZF/5cTBuMpJDpNschA@public.gmane.org>
To: linux-nfs@vger.kernel.org
Subject: NFS problem after upgrade from 2.6.32 to 2.6.3[3-7]
Date: Thu, 18 Nov 2010 11:31:09 +0100 [thread overview]
Message-ID: <x2e1v6i7wk2.fsf@anakin.ifi.uio.no> (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?
--
Henrik Grindal Bakken <hgb-6miFZF/5cTBuMpJDpNschA@public.gmane.org>
PGP ID: 8D436E52
Fingerprint: 131D 9590 F0CF 47EF 7963 02AF 9236 D25A 8D43 6E52
next reply other threads:[~2010-11-18 10:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 10:31 Henrik Grindal Bakken [this message]
2010-11-18 15:20 ` NFS problem after upgrade from 2.6.32 to 2.6.3[3-7] Chuck Lever
2010-11-19 14:24 ` Henrik Grindal Bakken
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x2e1v6i7wk2.fsf@anakin.ifi.uio.no \
--to=hgb-6mifzf/5ctbumpjdpnscha@public.gmane.org \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).