From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Eric B Munson <emunson@mgebm.net>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: NFS Regression in commit 0b26a0bf6ff398
Date: Tue, 15 Feb 2011 20:02:35 -0500 [thread overview]
Message-ID: <1297818155.10103.43.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <20110216005640.GA2841@mgebm.net>
On Tue, 2011-02-15 at 19:56 -0500, Eric B Munson wrote:
> While testing some 2.6.38 work my rsync backup script started consuming
> large amounts of memory (all available before dying with no more available
> memory). I have bisected the problem back to 0b26a0bf6ff398. I am
> unfamiliar with the NFS code so I don't know where to start looking for a
> possible fix. My backups files from my home directory to an NFS mounted
> directory. The NFS server is a Synology DS-411+ if it matters. Let me know
> if there is any other information I can provide.
Exactly which 2.6.38 kernel are you running, and which NFS version?
I'm having trouble seeing how the patch in question can be responsible
for what you are seeing, so please could you provide more details of
your test setup.
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
next parent reply other threads:[~2011-02-16 1:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110216005640.GA2841@mgebm.net>
2011-02-16 1:02 ` Trond Myklebust [this message]
2011-02-16 13:37 ` NFS Regression in commit 0b26a0bf6ff398 Eric B Munson
2011-02-24 19:57 ` Eric B Munson
2011-03-24 18:29 ` Eric B Munson
2011-04-06 21:31 ` Eric B Munson
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=1297818155.10103.43.camel@heimdal.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=emunson@mgebm.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@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;
as well as URLs for NNTP newsgroup(s).