From: Chuck Lever <chuck.lever@oracle.com>
To: Henrik Grindal Bakken <hgb@ifi.uio.no>
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFS problem after upgrade from 2.6.32 to 2.6.3[3-7]
Date: Thu, 18 Nov 2010 10:20:48 -0500 [thread overview]
Message-ID: <6B116440-2E1A-4E2A-9D56-EF30DAE5BD7E@oracle.com> (raw)
In-Reply-To: <x2e1v6i7wk2.fsf@anakin.ifi.uio.no>
On Nov 18, 2010, at 5:31 AM, Henrik Grindal Bakken wrote:
>
> 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.
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.
> 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@ifi.uio.no>
> 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 majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
next prev parent reply other threads:[~2010-11-18 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 10:31 NFS problem after upgrade from 2.6.32 to 2.6.3[3-7] Henrik Grindal Bakken
2010-11-18 15:20 ` Chuck Lever [this message]
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=6B116440-2E1A-4E2A-9D56-EF30DAE5BD7E@oracle.com \
--to=chuck.lever@oracle.com \
--cc=hgb@ifi.uio.no \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.