From: David Ford <david+powerix@blue-labs.org>
To: trond.myklebust@fys.uio.no,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Neil Brown <neilb@cse.unsw.edu.au>,
Andrew Morton <akpm@digeo.com>
Subject: Re: NFS problems, 2.5.5x
Date: Sat, 01 Feb 2003 08:03:39 -0800 [thread overview]
Message-ID: <3E3BEFDB.3060208@blue-labs.org> (raw)
In-Reply-To: <15931.35891.22926.408963@charged.uio.no>
The last time NFS was working, I had 2.4.19 and 2.5.53 clients on a
2.5.59 server, that was yesterday. I had experienced a slight problem
with it last week when my 2.5.53 client was booted for first time on
2.5.5x, it was previously a 2.4 kernel. The server OOPSed repeatedly
shortly after bootup in NFS stuff then it never happened again and was
rock solid until today.
David
Trond Myklebust wrote:
>>>>>>" " == David Ford <david+powerix@blue-labs.org> writes:
>>>>>>
>>>>>>
>
> > Synopsis: nfsserver:/home/david mount, get dir. entries loops
> > forever,
> > 2.5.59 for client and server.
>
> > Example: ls -l /home/david
>
> > An strace will show the same directory entries flying by over
> > and over until memory is exhausted or ^c comes along. It
> > worked at first for about 30 minutes while I finished the new
> > gentoo install on my desktop, but then things got weird. the
> > nfs server spat out a big long callback trace (oops) and died
> > hard. Had to reset the power. The looping started just
> > minutes before that. I've rebooted, tried 2.5.53 on the client
> > but no go.
>
>AFAICR, there have been no changes to the NFS client readdir code since
>2.5.30.
>
>Cheers,
> Trond
>
>
next prev parent reply other threads:[~2003-02-01 15:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-01 2:13 NFS problems, 2.5.5x David Ford
2003-02-01 2:30 ` Andrew Morton
2003-02-01 2:46 ` David Ford
2003-02-01 8:58 ` Trond Myklebust
2003-02-01 16:03 ` David Ford [this message]
2003-02-01 16:23 ` Trond Myklebust
2003-02-01 21:49 ` David Ford
2003-02-03 11:12 ` Oleg Drokin
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=3E3BEFDB.3060208@blue-labs.org \
--to=david+powerix@blue-labs.org \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=trond.myklebust@fys.uio.no \
/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.