From: Georg Ritter <newsgr.2007@gamebox.net>
To: nfs@lists.sourceforge.net
Subject: sco 5(server) linux(client, FC4) cp stalls after a few ten KBs
Date: Wed, 13 Dec 2006 02:44:06 +0100 [thread overview]
Message-ID: <457F5AE6.90900@gamebox.net> (raw)
Dear NFS gurus :-),
Problem:
FC4 box as client to a SCO 5 server stops copying after a few 10 KBs, worked on
same hardware with RH9 as client, and currently still works for a mdk10 client.
I would be grateful for a hint or better a way to fix it, as I have no idea of
what else could be wrong and where/how to investigate it further.
Longer description:
I ran into the following problem, after upgrading from RH9 to FC4 (and also
another FC6 box has the same "behaviour") and completely ran out of ideas.
Setup:
FC4/FC6 boxes as clients connecting to an SCO nfs server, small LAN, all class A
IPs.
Client can mount the exports from the SCO server, but after a few 10KB of data
the speed drops near or to zero and it gets stuck and still seems to copy a few
bytes every 30 secs or minute.
Findings so far:
mdk10 laptop as a client can mount the SCO dirs and copies full speed.
It used to work with the exact same hardware but RH9 instead of FC4/FC6.
Looks like a buffer gets filled and then it gets stuck.
nfsd on the SCO don't die away.
No errors on SCO portmap (-v -d) (additionally it worked before, and serves the
mdk10 box, without touching the settings on the SCO server)
setting the debugging output on FC4 to 32565 with echo into the according
/proc/... vars reveals no obvious error message.
No errors with nfsstat neither on SCO nor FC4.
Network is at good health.
It works the other way round (SCO as client mounting from FC4 box)
Disabled (on FC4) firewall and selinux. No such things on the SCO box.
Seem to be ok in principal because it mounts and copies fine up to the stop
after a few ten KBs.
Tried different kernels on the FC4 box (all plain vanilla kernels offered via
official update path)
Tried many different options on the mount command: vers=2, nolock different
package sizes, forcing tcp etc.: no effect
Thanks,
Georg
P.S. More details from the FC4 (client) box available (logfiles, etc).
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2006-12-13 0:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 1:44 Georg Ritter [this message]
2006-12-13 1:58 ` sco 5(server) linux(client, FC4) cp stalls after a few ten KBs Trond Myklebust
2006-12-13 20:56 ` Georg Ritter
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=457F5AE6.90900@gamebox.net \
--to=newsgr.2007@gamebox.net \
--cc=nfs@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.