From: Steffen Persvold <sp@scali.no>
To: trond.myklebust@fys.uio.no
Cc: lkml <linux-kernel@vger.kernel.org>,
nfs list <nfs@lists.sourceforge.net>,
Neil Brown <neilb@cse.unsw.edu.au>
Subject: Re: 2.4.8 NFS Problems
Date: Thu, 20 Dec 2001 15:40:35 +0100 [thread overview]
Message-ID: <3C21F863.5278841A@scali.no> (raw)
In-Reply-To: <3C21B30D.871B6BE4@scali.no> <15393.51009.856041.463215@charged.uio.no>
Trond Myklebust wrote:
>
> >>>>> " " == Steffen Persvold <sp@scali.no> writes:
>
> >> I've been getting random NFS EIO errors for a few months but
> >> now it's repeatable. Trying to copy a large file from one 2.4.8
> >> SMP box to another is consistently failing (at different
> >> offsets >each time).
>
> Please try the patch on
>
> http://www.fys.uio.no/~trondmy/src/2.4.17/linux-2.4.17-fattr.dif
>
> that fixes at least 1 such EIO error which was discovered using fsx.
>
I can do that, but since one of the clients reporting this problem is an Alpha machine running
2.2.19 the patch won't do much good (not that the patch is architecture dependent, but it's only for
2.4.17). Has this patch been there since 2.2 or is it a new "feature" in the "stable" #:) 2.4
kernels.
Regards,
--
Steffen Persvold | Scalable Linux Systems | Try out the world's best
mailto:sp@scali.no | http://www.scali.com | performing MPI implementation:
Tel: (+47) 2262 8950 | Olaf Helsets vei 6 | - ScaMPI 1.12.2 -
Fax: (+47) 2262 8951 | N0621 Oslo, NORWAY | >300MBytes/s and <4uS latency
next prev parent reply other threads:[~2001-12-20 14:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-20 9:44 2.4.8 NFS Problems Steffen Persvold
2001-12-20 11:10 ` Trond Myklebust
2001-12-20 14:40 ` Steffen Persvold [this message]
2001-12-20 20:27 ` Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2001-09-05 11:56 Mike Black
2001-09-07 11:49 ` Trond Myklebust
2001-09-07 12:05 ` Peter T. Breuer
2001-09-07 12:27 ` Trond Myklebust
2001-09-07 12:36 ` Trond Myklebust
2001-09-07 13:13 ` Mike Black
2001-09-07 14:42 ` Trond Myklebust
2001-09-07 15:46 ` Mike Black
2001-09-08 10:53 ` Trond Myklebust
2001-09-08 11:53 ` Mike Black
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=3C21F863.5278841A@scali.no \
--to=sp@scali.no \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
--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