mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Frank <mflt1@micrologica.com.hk>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: NFS io errors on transfer from system running 2.4 to system running 2.5
Date: Tue, 3 Jun 2003 19:12:51 +0800	[thread overview]
Message-ID: <200306031912.53569.mflt1@micrologica.com.hk> (raw)

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.

- 2-5 > 2.4 is OK!
- SRebootting, swapping kernel causes the error on the system running 2.4    
- Fast machine > slow machine or slow machine > fast machine
  is no different
- Both systems run same distribution 
- Encountered since 2.4.20 with about 2.5.64 (my first 2.5 kernel)

Example:

/temp contains a couple of crap files

system mhfl2 is running 2.5.6x to 2.5.70-mm3 mounted on
/mnt/mhfl2.

On system running 2.4.20 or 2.4.21-x:
  while ((1)); do cp -f /temp/* /mnt/mhfl2/temp; done

cp: cannot create regular file `/mnt/mhfl2/temp/blah: Input/output error
cp: writing `/mnt/mhfl2/temp/blah: Input/output error

Errors are random, so the files change every run, sometimes there are no errors,
sometimes thre are 3 errors

Q? Any (in)compatibility reason or should I investigate further?

Regards
Michael Frank 


             reply	other threads:[~2003-06-03 11:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-03 11:12 Michael Frank [this message]
     [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
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=200306031912.53569.mflt1@micrologica.com.hk \
    --to=mflt1@micrologica.com.hk \
    --cc=akpm@digeo.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®