From: Matt C <wago@phlinux.com>
To: Hugo Mills <hugo-lkml@carfax.org.uk>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
Meelis Roos <mroos@math.ut.ee>,
lkml <linux-kernel@vger.kernel.org>, <neilb@cse.unsw.edu.au>
Subject: Re: NFS server broken in 2.4.22-pre6?
Date: Tue, 29 Jul 2003 10:50:53 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0307291048590.189-100000@fubar.phlinux.com> (raw)
In-Reply-To: <20030726151956.GA11253@carfax.org.uk>
I don't know if this is related or not, but I noticed that on old
redhat-6.2 (glibc-2.1.3) systems, portmap dies instantly under 2.4.21+
kernels. Older 2.4.18 kernels worked fine. It exits with -EBADF. I can get
a complete strace if that's interesting. I tested the portmap binary from
redhat-7.2 (which works under redhat-7.2) in the 6.2 environment, and it
had the same problem, so it's not portmap itself.
-matt c
On Sat, 26 Jul 2003, Hugo Mills wrote:
> On Fri, Jul 25, 2003 at 10:05:33AM -0300, Marcelo Tosatti wrote:
> >
> >
> > On Thu, 24 Jul 2003, Meelis Roos wrote:
> >
> > > NFS serving seems to be broken in 2.4.22-pre6. I had 2 computers running
> > > 2.4.22-pre6 (x86, debian unstable current). Tried to acces them via NFS
> > > (using am-utils actually) from a 3rd computer, IO error. Tried to
> > > mount directly, mount: RPC: timed out. Rebooted one computer to 2.4.18
> > > and NFS started to work.
> > >
> > > No more details currently but I can test more thoroughly tomorrow.
> >
> > Meelis,
> >
> > Please report more details.
>
> I'm also having trouble with NFS, with a 2.4.22-pre6-ac1 server.
>
> I'm booting a diskless workstation (with a 2.4.21-ac1 client), and
> it will boot and mount the root filesystem. When I try to mount any
> other filesystems, the client reports
>
> mount: can't get address for vlad
>
> and loses the main NFS mount: attempts to access any file on the root
> filesystem gives stale NFS file handle errors. The failure to mount
> also breaks the server -- I can no longer boot the diskless client.
> Restarting the NFS server allows me to boot the client once again.
>
> Like Meelis, I'm also using Debian unstable, and I've tried with
> both the 1.0.3-1 and 1.0.5 versions of the nfs-tools on both machines.
> Both versions give the same error that I reported above.
>
> Hugo.
>
>
prev parent reply other threads:[~2003-07-29 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-24 17:29 Meelis Roos
2003-07-25 13:05 ` Marcelo Tosatti
2003-07-25 20:30 ` Meelis Roos
2003-07-25 21:02 ` Mike Fedyk
2003-07-26 15:19 ` Hugo Mills
2003-07-29 17:50 ` Matt C [this message]
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=Pine.LNX.4.44.0307291048590.189-100000@fubar.phlinux.com \
--to=wago@phlinux.com \
--cc=hugo-lkml@carfax.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=mroos@math.ut.ee \
--cc=neilb@cse.unsw.edu.au \
/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
all inboxes | Powered by JetHome®