All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Brandt <brandtc@psi5.com>
To: Ric Wheeler <rwheeler@redhat.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: fsck.ext4 taking months
Date: Tue, 29 Mar 2011 22:21:41 +0200	[thread overview]
Message-ID: <4D923F55.1010507@psi5.com> (raw)
In-Reply-To: <4D909E92.4080209@redhat.com>

Am 28.03.2011 16:43, schrieb Ric Wheeler:

> Sounds like a configuration that might well require lots of memory to
> cache your allocated inodes, etc. How much memory do you have in the
> box running fsck? Any sense (vmstat, etc) what the box is spending
> its time doing?

 100% CPU use as seen in top and ps.

 The first System had 1GB and the process used 680MB, a plain Ubuntu
with nothing else running.

 I tried another system with 4GB, at least 3GB free, the process still
uses only 680MB. Booted from a Knoppix-CD, nothing running except fsck,
vmstat says:

procs -----------memory---------- ---swap-- -----io---- -system--
----cpu----
 r  b   swpd   free   buff  cache   si   so    bi    bo   in   cs us sy
id wa
 1  0      0 1573456 797988 776484    0    0    13     8    7   18 41  5
53  2

-- 
Christian Brandt

 life is short and in most cases it ends with death
 but my tombstone will carry the hiscore

  parent reply	other threads:[~2011-03-29 20:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-27 11:28 fsck.ext4 taking months Christian Brandt
2011-03-28 14:43 ` Ric Wheeler
2011-03-29  6:03   ` Rogier Wolff
2011-03-29 20:26     ` Christian Brandt
2011-03-30  8:45       ` Rogier Wolff
2011-03-29 20:21   ` Christian Brandt [this message]
2011-03-28 15:07 ` Eric Sandeen
2011-03-28 15:47 ` Ted Ts'o
2011-03-29 22:02   ` Christian Brandt
2011-03-30  8:34     ` Rogier Wolff

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=4D923F55.1010507@psi5.com \
    --to=brandtc@psi5.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=rwheeler@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.