mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Frank <mflt1@micrologica.com.hk>
To: Andrew Ryan <genanr@emsphone.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS io errors on transfer from system running 2.4 to system running 2.5
Date: Tue, 3 Jun 2003 23:09:20 +0800	[thread overview]
Message-ID: <200306032309.21056.mflt1@micrologica.com.hk> (raw)
In-Reply-To: <20030603144257.GA31734@thumper2.emsphone.com>

On Tuesday 03 June 2003 22:42, Andrew Ryan wrote:
> On Tue, Jun 03, 2003 at 07:12:51PM +0800, Michael Frank wrote:
> > Speaking of weird errors:
> >
> > For the last few months I encounter this:
> >
> > When doing rsync or cp _from_ system running 2.4 _to_ system running 2.5
> > get Input/output error errors with random files.
> >
> > - Encountered since 2.4.20 with about 2.5.64 (my first 2.5 kernel)
>
> I am having a similar problem writing to NFS mounted non-linux system on
> kernels past 2.4.20-pre3.  I get an input/output error while writing.  I
> have sent email to Trond Myklebust (who made the changes between pre3 and
> pre4).  And he said to switch to using the TCP protocol for mounts.  That
> worked, but I should not have to do that because
>
> 1. It worked to 2.4.20pre3 without a problem
> 2. Other OSes such as FreeBSD do not have issues writing to other OSes
> using UDP soft mounts.
>
> To me, there is something wrong with the changes that went in in
> 2.4.20pre4, it should work as it does in pre3 and/or other unix OSes such
> as FreeBSD. We should not have to work around the problem with hard links
> or using TCP instead of UDP.
>

Error frequency does not change between copying from a 2400MHz@2.4 > 600Mhz@2.5 
and 600Mhz@2.4 > 2400MHz@2.5. IIRC, I had errors from a 200MHz@2.4 to a 1600Mhz@2.5 
too.

Even if I run them both against each other, the error only happens on 2.4 and
the frequency does not increase. This is not a simple timout problem.

I'll think it through and build some scripts so everone can reproduce it 
and test it out.


Regards
Michael



  reply	other threads:[~2003-06-03 14:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-03 11:12 Michael Frank
     [not found] ` <20030603122411.GB14947@unthought.net>
2003-06-03 12:43   ` Michael Frank
2003-06-03 12:52     ` Jakob Oestergaard
2003-06-03 13:01       ` Michael Frank
2003-06-03 13:26         ` Jakob Oestergaard
2003-06-16  0:56           ` Michael Frank
2003-06-03 14:42 ` Andrew Ryan
2003-06-03 15:09   ` Michael Frank [this message]
2003-06-03 16:10   ` Trond Myklebust
2003-06-03 16:35     ` Michael Frank
2003-06-04 20:57     ` Andrew Ryan

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=200306032309.21056.mflt1@micrologica.com.hk \
    --to=mflt1@micrologica.com.hk \
    --cc=genanr@emsphone.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®