From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: CaT <cat@zip.com.au>
Cc: linux-kernel@vger.kernel.org, neilb@cse.unsw.edu.au
Subject: Re: 2.5->2.4 nfs corrupts
Date: 10 Apr 2003 12:28:03 +0200 [thread overview]
Message-ID: <shs3ckqfxzg.fsf@charged.uio.no> (raw)
In-Reply-To: <20030410013349.GC467@zip.com.au>
>>>>> " " == cat <cat@zip.com.au> writes:
> 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
Unless you are using soft mounts (in which case problem == user error)
I suggest you try the latest (as of last night - probably late
afternoon Oz-time) bitkeeper. It contains a patch that has been posted
several times on this list against a 2.5. NFS client read corruption.
Cheers,
Trond
prev parent reply other threads:[~2003-04-10 10:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-10 1:33 2.5->2.4 nfs corrupts CaT
2003-04-10 1:44 ` 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 [this message]
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=shs3ckqfxzg.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=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).