public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Korty <joe.korty@ccur.com>
To: Vladimir Serov <vserov@infratel.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: NFS write got EIO on kernel starting from 2.4.19-pre4 (or -pre3 maybe)
Date: Tue, 1 Apr 2003 17:10:33 -0500	[thread overview]
Message-ID: <20030401221033.GA14678@rudolph.ccur.com> (raw)
In-Reply-To: <3E899128.2050200@infratel.com>

On Tue, Apr 01, 2003 at 05:16:24PM +0400, Vladimir Serov wrote:
> Hi Trond,
> Belive or not, I've got another NFS related problem. I'm getting EIO in 
> several programs (dd, make) writing relativly large file (several 
> megabytes) over NFS. I've tested several kernels to find out where this 
> problem was introdused. Here the list:

Hi Vladimir, Everyone,
  Try this patch.  The bug was introduced in 2.4.20-rc3.  It tends to show
up when a slow nfs server is used with a fast client.
Joe


diff -Nur prev/2.4-redhawk/fs/nfs/read.c curr/2.4-redhawk/fs/nfs/read.c
+++ curr/2.4-redhawk/fs/nfs/read.c	2003-04-01 17:04:18.000000000 -0500
+++ curr/2.4-redhawk/fs/nfs/read.c	2003-04-01 17:04:18.000000000 -0500
@@ -424,7 +424,8 @@
 				memset(p + count, 0, PAGE_CACHE_SIZE - count);
 				kunmap(page);
 				count = 0;
-				if (data->res.eof)
+				if (data->res.eof
+				|| (page_index(page) < (PAGE_CACHE_ALIGN(inode->i_size) >> PAGE_CACHE_SHIFT)))
 					SetPageUptodate(page);
 				else
 					SetPageError(page);

      parent reply	other threads:[~2003-04-01 21:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-01 13:16 NFS write got EIO on kernel starting from 2.4.19-pre4 (or -pre3 maybe) Vladimir Serov
2003-04-01 15:54 ` Trond Myklebust
2003-04-01 16:37 ` Trond Myklebust
2003-04-01 17:41   ` Vladimir Serov
2003-04-01 22:10 ` Joe Korty [this message]

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=20030401221033.GA14678@rudolph.ccur.com \
    --to=joe.korty@ccur.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    --cc=vserov@infratel.com \
    /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