From: Martin Spott <Martin.Spott@uni-duisburg.de>
To: nfs@lists.sourceforge.net
Subject: Re: 2.6.0-test3-bk10-final regression getting out of hand
Date: 1 Nov 2003 16:29:52 GMT [thread overview]
Message-ID: <bo0n20$c3q$1@foehn.quickstep.oche.de> (raw)
In-Reply-To: 20031031214851.0d6e604b.lista2@comhem.se
Voluspa <lista2@comhem.se> wrote:
> I'm experiencing a serious NFS regression since 2.6.0-test3-bk10-final
> (bk-set determined now). Since that, along the road to 2.6.0-test9,
> something has gotten completely out of hand.
I can second the experiences on heavy trouble with 2.6.0-test[8,9] as
NFS _client_ against 2.4.2[1,2] as a server. I didn't have different
servers for testing against but I pretty much _believe_ it's a client
issue.
I only sticked to 'official' 2.6.0-test patches and I'd like to
express, that beginning with 2.6.0-test8 the NFS client is absolutely
unsuable for me. Trying to copy (with 'cp') a file from a local
filesystem to the server over NFS.V2 or .V3 completely freezes _any_
NFS traffic with the same server.
Are there any significant changes to the NFS client I should back out
for the purpose of finding the 'bug' ?
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-11-01 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-31 20:48 2.6.0-test3-bk10-final regression getting out of hand Voluspa
2003-11-01 16:29 ` Martin Spott [this message]
2003-11-04 6:35 ` Trond Myklebust
2003-11-04 16:34 ` Robert Williamson
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='bo0n20$c3q$1@foehn.quickstep.oche.de' \
--to=martin.spott@uni-duisburg.de \
--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.