From: foo@porto.bmb.uga.edu
To: linux-kernel@vger.kernel.org
Subject: Re: NFS problem with recent 2.6 kernels (also serial console weirdness)
Date: Wed, 16 Jun 2004 15:20:55 -0400 [thread overview]
Message-ID: <20040616192055.GC14580@porto.bmb.uga.edu> (raw)
In-Reply-To: <20040615000436.GA12516@porto.bmb.uga.edu>
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.
-ryan
next prev parent reply other threads:[~2004-06-16 19:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 0:04 NFS problem with recent 2.6 kernels (also serial console weirdness) foo
2004-06-15 18:42 ` more about serial console foo
2004-06-15 18:52 ` Russell King
2004-06-15 19:00 ` foo
2004-06-16 19:20 ` foo [this message]
2004-06-17 1:43 ` NFS problem with recent 2.6 kernels (also serial console weirdness) foo
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=20040616192055.GC14580@porto.bmb.uga.edu \
--to=foo@porto.bmb.uga.edu \
--cc=linux-kernel@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.