mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Fred Tyler" <fredty8@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Slow, persistent memory leak in 2.6.20
Date: Sun, 26 Aug 2007 12:14:40 -0400	[thread overview]
Message-ID: <466ad3f90708260914v7d11ebc2s8025ea5d549683dd@mail.gmail.com> (raw)
In-Reply-To: <466ad3f90708260914g3cb92f30q8d5672e3f9cf960c@mail.gmail.com>

On 8/26/07, Fred Tyler <fredty8@gmail.com> wrote:
> On 8/26/07, Jan Engelhardt <jengelh@computergmbh.de> wrote:
> >
> > On Aug 26 2007 11:51, Fred Tyler wrote:
> > >On 8/26/07, Fred Tyler <fredty8@gmail.com> wrote:
> > >> I think I've come across a memory leak in 2.6.20. I've upgraded to the
> > >> latest 2.6.20.17, but it didn't seem to help.
> > >
> > >Sorry to keep replying to my own post, but further investigation
> > >suggests that the memory losses may be occurring at times of heavy
> > >filesystem access. The machines in question run rsyncs of hundreds of
> > >thousands of files every few hours, and I'm starting to think that the
> > >memory loss occurs during these times. I don't know how I'd go about
> > >proving this though...
> >
> > Please rule out filesystem caches by issuing
> >         sync;
> >         echo 3 >/proc/sys/vm/drop_caches;
>
>
> Ok, I did this on a non-production machine that has only been up for a
> few hours, and here's what happened:
>
> ======== Before =========
>
> $ free -m
>              total       used       free     shared    buffers     cached
> Mem:           878        824         54          0        111        422
> -/+ buffers/cache:        290        587
> Swap:           63          0         63
>
>
> ======== After ========
>
> root@b0$ free -m
>              total       used       free     shared    buffers     cached
> Mem:           878         47        830          0          6          4
> -/+ buffers/cache:         36        841
> Swap:           63          0         63
>
> ======================
>
> So, I guess it worked? (I don't know what was supposed to happen, but
> memory usage dropped significantly when I did this.)
>
> However, I'm not sure this staging machine has been up long enough or
> doing enough to exhibit the problem. I can try this on my production
> servers (the ones I provided graphs for) late tonight, but how safe is
> running this command? Does it permanently disable file caching? Do I
> need to reset it afterwards? If I stop all services (databases,
> logging, etc) first, am I protected against data loss?
>

  parent reply	other threads:[~2007-08-26 16:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-26 14:39 Fred Tyler
2007-08-26 15:32 ` Alexey Dobriyan
2007-08-26 15:40 ` Fred Tyler
2007-08-26 15:51 ` Fred Tyler
2007-08-26 15:52   ` Jan Engelhardt
     [not found]     ` <466ad3f90708260914g3cb92f30q8d5672e3f9cf960c@mail.gmail.com>
2007-08-26 16:14       ` Fred Tyler [this message]
2007-08-26 16:16     ` Fred Tyler
2007-08-26 16:30       ` Jan Engelhardt
2007-08-26 16:49         ` Fred Tyler
2007-08-26 16:58           ` Jan Engelhardt
2007-08-26 16:58         ` Fred Tyler
2007-08-26 17:42           ` Jan Engelhardt
2007-08-26 17:03       ` Denys Vlasenko
2007-08-26 17:41         ` Fred Tyler
2007-08-26 17:44           ` Jan Engelhardt
2007-08-26 22:16 ` Jesper Juhl

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=466ad3f90708260914v7d11ebc2s8025ea5d549683dd@mail.gmail.com \
    --to=fredty8@gmail.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®