From: Ben Hutchings <ben@decadent.org.uk>
To: linux-nfs@vger.kernel.org
Cc: 600871@bugs.debian.org, Oleksiy Vasylyuk <o.vasylyuk@osorno.ca>
Subject: Bug#600871: nfs-common: Very slow and unreliable performance of GUI(KDE) when /home nfs mounted
Date: Wed, 27 Oct 2010 01:38:05 +0200 [thread overview]
Message-ID: <1288136285.4010.27.camel@localhost> (raw)
In-Reply-To: <201010261059.58090.o.vasylyuk@osorno.ca>
[-- Attachment #1: Type: text/plain, Size: 419 bytes --]
Oleksiy Vasylyuk reported severe performance degradation of KDE on an
NFS client on Linux 2.6.26 after upgrading nfs-utils from version 1.1.2
to 1.2.2. Some additional details are logged at
<http://bugs.debian.org/600871>.
Does anyone recognise this problem, or can someone suggest how to
investigate further?
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
parent reply other threads:[~2010-10-26 23:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <201010261059.58090.o.vasylyuk@osorno.ca>]
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=1288136285.4010.27.camel@localhost \
--to=ben@decadent.org.uk \
--cc=600871@bugs.debian.org \
--cc=linux-nfs@vger.kernel.org \
--cc=o.vasylyuk@osorno.ca \
/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).