public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Pittman <daniel@rimspace.net>
To: linux-kernel@vger.kernel.org
Subject: Linux <-> Linux NFS issues.
Date: Fri, 21 Mar 2003 21:37:13 +1100	[thread overview]
Message-ID: <87isudm2ee.fsf@enki.rimspace.net> (raw)

I am sharing large volume data between two Linux machines using NFS v3,
and have a bit of a reliability issue with it, with writes on the client
machine failing occasionally.


The server is running:
Linux gavroche 2.5.64 #2 Fri Mar 7 20:11:43 EST 2003

The client is running:
Linux anu 2.5.64 #6 Mon Mar 17 19:08:37 EST 2003

Both are .64 + a few csets after that, but the problem was evident with
.62 or so as well.  I am not confident enough to say it started then,
though, as I believe it happened with an earlier version on the client.


The client machine reports, in dmesg:

NFS: server cheating in read reply: count 4096 > recvd 1000

The 'count' value is occasionally higher, but not often, and the 'recvd'
never seems to differ from 1000.


On the client, a write or close syscall returns an error, specifically
'Input/Output Error' (from perror, so -EIO is the code).


This usually happens somewhere between one and ten hours through the
encoding of a set of DV files to MPEG2, and at different spots in the
process.


Searching the archives shows that this problem has been seen before, but
didn't turn up anything that was a solution.

       Daniel

-- 
Specialized meaninglessness has come to be regarded,
in some circles, as a kind of hallmark of true science.
        -- Aldous Huxley

             reply	other threads:[~2003-03-21 10:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-21 10:37 Daniel Pittman [this message]
2003-03-21 12:32 ` Linux <-> Linux NFS issues Dave Jones
2003-03-21 12:52   ` Trond Myklebust
2003-03-21 12:57     ` Dave Jones

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=87isudm2ee.fsf@enki.rimspace.net \
    --to=daniel@rimspace.net \
    --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