From: Andy <genanr@emsphone.com>
To: linux-kernel@vger.kernel.org
Subject: File Corruption Linux -> Novell NFS
Date: Tue, 15 Jun 2004 14:01:15 -0500 [thread overview]
Message-ID: <20040615190114.GA13756@thumper2> (raw)
After the XFS/NFS issue got resolved, I was able to focus my testing to the
other NFS corruption I was seeing. All the test does is copy a file to
novell, then compares the remote copy to the local (XFS fs) one. The corruption only
occurs sometimes and tends to be on an 8k boundary, but not always. And
NO, this is not a network problem, since I don't see the corruption on a
FreeBSD (FreeBSD->novell NFS) box which is on the same network. I have also
seen it on systems with different network cards (intel and broadcom gigabit
cards). I have seen this on kernels 2.4.22 & 2.4.26.
Another problem I see is when deleting from an NFS mounted tru64 system. I
often get a "no such file or directory" error when I delete the file even
though a ls right before the delete shows the file there. And after the
delete, the file is no longer in the directory, even though the delete
claimed the file wasn't there, it still deleted the file. I have not seen
file corruption to a tru64 box.
Andy
reply other threads:[~2004-06-15 19:06 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=20040615190114.GA13756@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