public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Lost free space on /
Date: Wed, 10 Jun 2009 13:55:16 -0500	[thread overview]
Message-ID: <58965d8a0906101155n46ce6d04q878e2b0cc531403c@mail.gmail.com> (raw)
In-Reply-To: <dd6ae1990906101124j1a3b6367g59a81419297a89e3@mail.gmail.com>

On Wed, Jun 10, 2009 at 1:24 PM, Alexander
Pilipovsky<alexander.pilipovsky@gmail.com> wrote:
>
>
> 2009/6/10 Justin <justin@j-schmitz.net>
>>
>> Alexander Pilipovsky schrieb:
>> ....
>>
>> You have something big in /var. Check /var/tmp/portage or /var/log.
>>
>> Alos test sys-fs/ncdu or similar tools.
>>
>
> Thanks, it's was /var/log/messages that had 11 GB and was not opened by any
> editor.

I had a similar problem, 100% cpu usage caused by a daemon that did
not respond well when network connection was lost. My
/var/log/messages grew over 60GB in a few hours with the same message
repeated tens of millions of times. I changed my logger from syslog-ng
to metalog, which suppresses duplicates, and now it's not a problem.



  reply	other threads:[~2009-06-10 18:55 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-10 18:07 [gentoo-user] Lost free space on / Alexander Pilipovsky
2009-06-10 18:12 ` Justin
2009-06-10 18:24   ` Alexander Pilipovsky
2009-06-10 18:55     ` Paul Hartman [this message]
2009-06-10 19:31       ` Alexander Pilipovsky
2009-06-10 19:40       ` Dirk Heinrichs
2009-06-10 19:50         ` Alexander Pilipovsky
2009-06-10 20:21           ` Alan McKinnon
2009-06-10 20:49             ` Volker Armin Hemmann
2009-06-10 21:09               ` Dirk Heinrichs
2009-06-10 22:47                 ` Dale
2009-06-10 21:24             ` KH
2009-06-10 21:29               ` Alan McKinnon
2009-06-10 23:37                 ` KH
2009-06-11 16:03                   ` bn
2009-06-11 16:09                     ` Alexander Pilipovsky
2009-06-11 16:32                       ` Mick
2009-06-12 10:42                       ` KH
2009-06-12 10:48                     ` KH
2009-06-12 10:58                       ` Alan McKinnon
2009-06-12 12:59                         ` Etaoin Shrdlu
2009-06-12 16:05                           ` Dale
2009-06-12 19:56                             ` Alan McKinnon
2009-06-12 20:24                               ` Dirk Heinrichs
2009-06-13  9:07                                 ` Alan McKinnon
2009-06-13 10:08                               ` Neil Bothwick
2009-06-10 21:48           ` Paul Hartman
2009-06-10 22:44             ` Philip Webb
2009-06-11  7:06               ` Dirk Heinrichs
2009-06-11  7:24                 ` Volker Armin Hemmann
2009-06-11  7:33                 ` [gentoo-user] " Nikos Chantziaras
2009-06-11  7:40                   ` Dirk Heinrichs
2009-06-11  7:49                     ` Volker Armin Hemmann
2009-06-11  8:02                       ` Dirk Heinrichs
2009-06-11  8:17                     ` Nikos Chantziaras
2009-06-11 13:52                       ` Mike Kazantsev
2009-06-11 14:16                         ` Nikos Chantziaras
2009-06-10 19:56         ` [gentoo-user] " KH
2009-06-10 20:01           ` Dirk Heinrichs
2009-06-10 20:25           ` Dale
2009-06-10 19:56         ` Paul Hartman
2009-06-10 18:45 ` Dale
2009-06-10 19:27   ` Alexander Pilipovsky

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=58965d8a0906101155n46ce6d04q878e2b0cc531403c@mail.gmail.com \
    --to=paul.hartman+gentoo@gmail.com \
    --cc=gentoo-user@lists.gentoo.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