From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Oleg Drokin <green@namesys.com>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
David Ford <david+powerix@blue-labs.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Current NFS issues (2.5.59)
Date: Tue, 11 Feb 2003 13:23:51 +0100 [thread overview]
Message-ID: <15944.60247.512630.175678@charged.uio.no> (raw)
In-Reply-To: <20030211100011.A5850@namesys.com>
>>>>> " " == Oleg Drokin <green@namesys.com> writes:
>> 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.
...and I am unable to reproduce this 8-)
I have a feeling that something is still not right in the IPv4 socket
layer. There are odd memory corruptions etc which I don't see on the
same code in 2.4.x.
Still hunting though, so I may yet find the problems were in my own
code...
Cheers,
Trond
next prev parent reply other threads:[~2003-02-11 12:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-09 23:18 David Ford
2003-02-11 4:05 ` Neil Brown
2003-02-11 7:00 ` Oleg Drokin
2003-02-11 12:23 ` Trond Myklebust [this message]
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=15944.60247.512630.175678@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=david+powerix@blue-labs.org \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--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®