From: Eric B Munson <emunson@mgebm.net>
To: Trond.Myklebust@netapp.com
Cc: nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: NFS Regression in commit 0b26a0bf6ff398
Date: Tue, 15 Feb 2011 19:56:40 -0500 [thread overview]
Message-ID: <20110216005640.GA2841@mgebm.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 494 bytes --]
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.
Eric
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next reply other threads:[~2011-02-16 0:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 0:56 Eric B Munson [this message]
2011-02-16 1:02 ` NFS Regression in commit 0b26a0bf6ff398 Trond Myklebust
2011-02-16 13:37 ` 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=20110216005640.GA2841@mgebm.net \
--to=emunson@mgebm.net \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox