public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Kletschke <lists@ku-gbr.de>
To: linux-kernel@vger.kernel.org
Subject: nfs4v stalls transfering files, stalls
Date: Mon, 25 Aug 2008 14:32:02 +0200	[thread overview]
Message-ID: <20080825123202.GC2497@anita> (raw)

Recently I experience oddities with my home nfsv4 client/server
connection which worked long very well. I don't know exactly with which
version it begun. I experienced once in a while, that I delete files but
after rebooting the computers the next day or after doing an ls on the
directory, the files are still there. While I did not take this sriously
first I now have the problem copying an ~600MB avi onto the nfs share.
After 25M or 30M (each time after this amount already transferred) the
connection stalls:

nfs: server 10.10.0.1 not responding, timed out

On my client I have 2.6.17_rc3 and this fstab entry:

10.10.0.1:/pub/ /pub nfs4 tcp,async,hard,intr,noauto,user,sec=sys 0 0

this is only an example, I tried udp, soft and timeo=8 instead of hard
and intr.

On server I had 2.6.25 with this exports:

/exports
10.10.0.0/255.255.0.0(rw,fsid=0,insecure,no_subtree_check,sync)
/exports/pub
10.10.0.0/255.255.0.0(rw,nohide,insecure,no_subtree_check,async)

When this happened, the server had this in dmesg:

RPC: bad TCP reclen 0x0010011a (non-terminal)

or:

RPC: bad TCP reclen 0x3b468abe (large)

In 2.6.27_rc (runnning now), the part in svchost.c was spelled other, it
says now:

RPC: fragment too large: 0x6be367a9
or
RPC: fragment too large: 0x1287087c

Starting the nfs stuff yields into

RPC: multiple fragments per record not supported

with no other regression though.


What can I do to narrow this down?

Kind Regards, Konsti

-- 
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E  A080 1E69 3FDA EF62 FCEF

             reply	other threads:[~2008-08-25 13:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-25 12:32 Konstantin Kletschke [this message]
2008-08-25 19:33 ` nfs4v stalls transfering files, stalls Konstantin Kletschke

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=20080825123202.GC2497@anita \
    --to=lists@ku-gbr.de \
    --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