From: CaT <cat@zip.com.au>
To: linux-kernel@vger.kernel.org
Cc: neilb@cse.unsw.edu.au
Subject: 2.5->2.4 nfs corrupts
Date: Thu, 10 Apr 2003 11:33:49 +1000 [thread overview]
Message-ID: <20030410013349.GC467@zip.com.au> (raw)
nfs server: 2.4.21-pre2
nfs client: 2.5.67
Every now and then I have problems copying data to and from the nfs
mount. It can either result in aborted writes like this:
15 [11:23:59] >> mv maestro.mpeg /share/funny
mv: closing `/share/funny/maestro.mpeg': Input/output error
15 [11:24:24] >> cp maestro.mpeg /share/funny
(it succeeded on the 2nd go)
or reads where unzip failed to unzip a file across the nfs link. there's
nothing in dmesg on either side of the fence to indicate problems and
while there was no message in the logs today, yesterday when I was
writing to the nfs server and got some corrupt files tyhis was logged:
messages:Apr 9 11:50:19 theirongiant kernel: nfs: server bob not responding, timed out
messages:Apr 9 13:15:29 theirongiant kernel: nfs: server bob not responding, timed out
But this is a local lan and the pc was never unplugged nor do problems
come up in anything else at any other time. The eepro driver didn't
detect a disconnection either.
Hope this helps. I'll do some more digging if someone can tell me what
to dig with and how. This is all I can think of atm.
--
Martin's distress was in contrast to the bitter satisfaction of some
of his fellow marines as they surveyed the scene. "The Iraqis are sick
people and we are the chemotherapy," said Corporal Ryan Dupre. "I am
starting to hate this country. Wait till I get hold of a friggin' Iraqi.
No, I won't get hold of one. I'll just kill him."
- http://www.informationclearinghouse.info/article2479.htm
next reply other threads:[~2003-04-10 1:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-10 1:33 CaT [this message]
2003-04-10 1:44 ` 2.5->2.4 nfs corrupts Dave Jones
2003-04-10 4:20 ` CaT
2003-04-10 7:50 ` Petition against EU software patents Giuliano Pochini
2003-04-10 8:20 ` 2.5->2.4 nfs corrupts Erik Hensema
2003-04-10 10:28 ` Trond Myklebust
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=20030410013349.GC467@zip.com.au \
--to=cat@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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;
as well as URLs for NNTP newsgroup(s).