From: Andy <genanr@emsphone.com>
To: linux-kernel@vger.kernel.org
Subject: NFS corruption in 2.4.x, not 2.6.7
Date: Wed, 30 Jun 2004 15:38:21 -0500 [thread overview]
Message-ID: <20040630203821.GA12223@thumper2> (raw)
Repeated copy and compare operations from linux to novell or tru64 systems
cause occasional corruption to the file copied. This problem has occurred
in all the 2.4.x kernels I've tried 2.4.20-2.4.27-rc2 (I did not try all of
them, but several), however, I have yet to run into the problem on the
2.6.7 kernel.
I would like to stick with 2.4.x kernel, for now, since I would like to
continue using the qlogic drivers with failover. The new device-mapper
multipath stuff (needed for failover now) in the 2.6+patches kernels, just
is not ready yet (I need to test it more).
Sniffing packets going between the linux and novell server with tcpdump in
the middle, the data going to the novell server appears correct. The data
that was corrupted was retransmitted, both packets look correct.
I noticed that the 2.4.x kernels send fragments backwards (i.e. offset 0, is
the last fragment sent) while the 2.6.7 kernel sends fragments with
increasing offsets.
Initially this seems like a novell problem, but the fact that 2.6.7 seems to
work and that the problem also occurs copying to tru64, points to a linux
2.4 series problem. Any ideas on what changed between 2.4 and 2.6 that
could have fixed this?
Andy
reply other threads:[~2004-06-30 20:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040630203821.GA12223@thumper2 \
--to=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