From: Oleg Drokin <green@namesys.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: David Ford <david+powerix@blue-labs.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: Current NFS issues (2.5.59)
Date: Tue, 11 Feb 2003 10:00:11 +0300 [thread overview]
Message-ID: <20030211100011.A5850@namesys.com> (raw)
In-Reply-To: <15944.30340.955911.798377@notabene.cse.unsw.edu.au>
Hello!
On Tue, Feb 11, 2003 at 03:05:24PM +1100, Neil Brown wrote:
> > 3. Mount point F (/home/david) infrequently loops. ls -la /home/david
> > will loop forever until all client memory is exhausted and the kernel
> > kills it via OOM. ls -la /home/david/somefile or /home/david/somedir/
> > works just fine as well as any sub directory under /home/david.
> > Restarts of both systems refuse to fix things.
> I think this might be a reiserfs problem. Someone else mentioned that
I was not able to reproduce that.
> this started happening when they upgrade from an earlier 2.5 kernel.
I think that earlier report was from David too. This is just more detailed
report it seems.
And while you are listening - I want to share my own NFs problems in 2.5.59 ;)
If I try to mount any NFS exported filesystem from the same host (e.g
localhost), mount process hangs in D state. Server appears to work ok though
and serves requests from external clients.
Bye,
Oleg
next prev parent reply other threads:[~2003-02-11 6:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-09 23:18 Current NFS issues (2.5.59) David Ford
2003-02-11 4:05 ` Neil Brown
2003-02-11 7:00 ` Oleg Drokin [this message]
2003-02-11 12:23 ` Trond Myklebust
2003-02-11 13:31 ` Oleg Drokin
2003-02-11 22:12 ` Neil Brown
2003-02-12 0:05 ` Trond Myklebust
2003-02-12 0:20 ` David Ford
2003-02-11 16:55 ` David Ford
2003-02-11 22:32 ` Neil Brown
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=20030211100011.A5850@namesys.com \
--to=green@namesys.com \
--cc=david+powerix@blue-labs.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox