Date: Wed, 16 Jun 2004 21:43:06 -0400
To: linux-kernel@vger.kernel.org
Subject: Re: NFS problem with recent 2.6 kernels (also serial console weirdness)
Message-ID: <20040617014306.GB14663@porto.bmb.uga.edu>
Reply-To: foo@porto.bmb.uga.edu
References: <20040615000436.GA12516@porto.bmb.uga.edu> <20040616192055.GC14580@porto.bmb.uga.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040616192055.GC14580@porto.bmb.uga.edu>
User-Agent: Mutt/1.5.5.1+cvs20040105i
From: foo@porto.bmb.uga.edu
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1631
Lines: 39

On Wed, Jun 16, 2004 at 03:20:55PM -0400, foo wrote:
> On Mon, Jun 14, 2004 at 08:04:36PM -0400, foo@porto.bmb.uga.edu wrote:
> > Hello, I have an x86_64 NFS server with a 32-bit userspace (debian
> > woody+backports as necessary) that starts to refuse mount requests after
> > a while (sometimes no time at all),  The symptom from the client side
> > (tested with Linux 2.6, and Solaris 9) is this:
> > 
> > mount: RPC: Unable to receive; errno = Connection refused
> 
> This still happens with 2.6.7.  I did
> 
> umount -a -t nfs; mount -a
> 
> on a client and I had to restart the NFS server, portmap, etc. 4 times
> to get everything mounted again.

Hmm, so I didn't see this in the logs (a result of the above):

rpc.mountd[752]: segfault at 000000004b87ad6e rip 00000000080503e9 rsp 00000000ffffd684 error 4
nfsd: last server has exited
nfsd: unexporting all filesystems
rpc.mountd[3959]: segfault at 000000004b87ad6e rip 00000000080503e9 rsp 00000000ffffd494 error 4
nfsd: last server has exited
nfsd: unexporting all filesystems
rpc.mountd[3996]: segfault at 000000004b87ad6e rip 00000000080503e9 rsp 00000000ffffd494 error 4
nfsd: last server has exited
nfsd: unexporting all filesystems
rpciod: active tasks at shutdown?!
RPC: error 5 connecting to server localhost
RPC: failed to contact portmap (errno -5).

Is this a bug in mountd, then?  If so, sorry for the noise.

-ryan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/