From: Vladimir Serov <vserov@infratel.com>
To: trond.myklebust@fys.uio.no
Cc: 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, 01 Apr 2003 21:41:23 +0400 [thread overview]
Message-ID: <3E89CF43.2030801@infratel.com> (raw)
In-Reply-To: 16009.49199.898453.578446@charged.uio.no
Trond Myklebust wrote:
>>>>>>" " == Vladimir Serov <vserov@infratel.com> writes:
>>>>>>
>>>>>>
>
> > 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.
>
>You sure about the 'regardless of hard mount' bit? I can write
>multi-gigabyte files with 2.4.21-pre6 without ever seeing an error
>(just now I ran a 3x3GB read/write using iozone without any trouble).
>
>Cheers,
> Trond
>
Hi,Trond
I know myself that NFS is rather reliable for many yers, I was working
for many years in HEP community (CERN/ALICE,FNAL/D0,JLAB/CLAS) and used
NFS all the way processing uncounted terrabytes of data. BUT !!!
Something in my current setup is triggering some hard to exibit problem.
Mine previous problem with ARM board for example shows on ten physically
different boards with several PC different in hardware and software. I
really don't think it's only hardware problem (but it could be hardware
related, i mean 3COM NIC's can somehow brighten this problem). Well , I
don't really know what the hell is going on, That's why I'm calling for
assistance.
Regards, Vladimir
next prev parent reply other threads:[~2003-04-01 17:30 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 [this message]
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=3E89CF43.2030801@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