From: Vladimir Serov <vserov@infratel.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>,
lkml <linux-kernel@vger.kernel.org>
Subject: NFS write got EIO on kernel starting from 2.4.19-pre4 (or -pre3 maybe)
Date: Tue, 01 Apr 2003 17:16:24 +0400 [thread overview]
Message-ID: <3E899128.2050200@infratel.com> (raw)
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:
Good kernels (doesn't give EIO) : 2.4.18-5asp, 2.4.19, 2.4.20-pre2
Bad kernel (gives EIO): 2.4.20-pre4, 2.4.20-pre6, 2.4.20,
2.4.21-pre5-ac3, 2.4.21-pre6
2.4.20-pre3 unfortunatly hangs on boot on my hardware.
I'm able to trigger problem by 'dd if=/dev/zero of=test bs=32k count=1024'
I'm using NFS over UDP, and this problem ccured regardless of soft or
hard mounted fs.
There was no changes in eepro100 driver i'm using for NIC between
2.4.20-pre2 and 2.4.20-pre4
client hardware : Intel mobo with built-in NIC , P4 2.2Ghz, 512 Mb DDR
memory
server hardware: MSI i815ept mobo with 3Com 3c905C-TX/TX-M [Tornado]
PIII 733Mhz , 512Mb SDRAM
client and server are on the same 100Mb hub , client is under ASP Linux
7.3, server is under RH8.0
Unfortunatly, dd or cp problem is transient , while make (actually ar)
gets EIO when building openh323 just every time.
I have to stick to the more recent then 2.4.20-pre2 kernel to make
CD/DVD writer working on the other hand.
Can You investigate this problem or give me an advise what to do myself ?
By the way , do You have any progress with nfsclient hanging in the D
state, i've told You previously ?
Cheers, Vladimir.
next reply other threads:[~2003-04-01 13:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 13:16 Vladimir Serov [this message]
2003-04-01 15:54 ` NFS write got EIO on kernel starting from 2.4.19-pre4 (or -pre3 maybe) Trond Myklebust
2003-04-01 16:37 ` Trond Myklebust
2003-04-01 17:41 ` Vladimir Serov
2003-04-01 22:10 ` Joe Korty
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=3E899128.2050200@infratel.com \
--to=vserov@infratel.com \
--cc=linux-kernel@vger.kernel.org \
--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