From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.60 NFS FSX
Date: 13 Feb 2003 16:45:27 +0100 [thread overview]
Message-ID: <shs4r78yyjs.fsf@charged.uio.no> (raw)
In-Reply-To: <20030213152742.GA1560@codemonkey.org.uk>
>>>>> " " == Dave Jones <davej@codemonkey.org.uk> writes:
> 2.5.60's NFS seems to have various issues. (2.5.60 client,
> 2.4.21pre3 server)
> - I ran an fsx and an fsstress in parallel.
> Client rebooted after 2-3 minutes.
I know. There's memory corruption going on somewhere, but I'm not sure
exactly where.
> - fsx on its own, after quite a while, this happens..
Also known. It's a bit odd really: the reads fail due to some form of
corruption, but the writes are OK. Means that when you later come to
compare the '.fsxgood' file to the 'bad' file, then things look OK.
I'm a bit confused w.r.t. both these issues. Neither occur on the
2.4.x platform despite the fact that the code is more or less the
same. This is why I suspect an IPv4 socket problem.
Cheers,
Trond
next prev parent reply other threads:[~2003-02-13 15:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 15:27 2.5.60 NFS FSX Dave Jones
2003-02-13 15:45 ` Trond Myklebust [this message]
2003-02-13 15:51 ` Dave Jones
2003-02-13 16:04 ` Trond Myklebust
2003-02-13 16:05 ` Dave Jones
2003-02-13 18:54 ` Joel Becker
2003-02-13 19:08 ` Trond Myklebust
2003-02-13 19:27 ` Dave Jones
[not found] ` <20030213204906.GA24109@codemonkey.org.uk>
2003-02-13 21:12 ` Trond Myklebust
2003-02-13 21:30 ` Dave Jones
2003-02-13 22:05 ` Dave Jones
2003-02-13 22:15 ` Dave Jones
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=shs4r78yyjs.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=davej@codemonkey.org.uk \
--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.