mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel@ddx.a2000.nu
To: linux-kernel@vger.kernel.org
Cc: linux-raid@vger.kernel.org
Subject: fsck out of memory
Date: Fri, 7 Feb 2003 16:17:35 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.53.0302071555110.718@ddx.a2000.nu> (raw)

i'm trying to run e2fsk after a system hang
after 1 hour running (70%) which had a memory usage for about 128M
i get these errors in the dmesg :

Out of Memory: Killed process 732 (fsck.ext2).
Out of Memory: Killed process 732 (fsck.ext2).
Out of Memory: Killed process 732 (fsck.ext2).
Out of Memory: Killed process 732 (fsck.ext2).

and this some pages

top gives me this info for fsck.ext2 :

  732 root       9   0  592M 465M  2068 S    64.7 92.6   6:31 fsck.ext2

Mem:   514360K av,  512176K used,    2184K free,       0K shrd,     564K
buff
Swap:  136544K av,  136544K used,       0K free                    3120K
cache

system has 512Megabyte memory (and 128mb swap (only fileserver, never
needed more swap)

I really wonder if there is something wrong with e2fsk ?
does it really need that much memory ?
(fsck on 2.2TB /dev/md0)

it was putting a lot of info on the screen (for some minutes) :
Duplicate/bad block in inode ... / ... ...  ... ... ...
(and scrolling in real fast speed)

e2fsprogs version 1.27 with kernel 2.4.20 (+lbd patch)
i tried upgrading e2fsutils to 1.32 (latest version), but this doesn't
help

any hints ? (maybe a way to disable the enormous output from
'Duplicate/bad block in inode ..' ?)

(also why does it tell, killed when it stays running (otherwise it can't
kill multiple times...))

             reply	other threads:[~2003-02-07 15:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-07 15:17 kernel [this message]
2003-02-07 17:07 ` Stephan van Hienen
2003-02-07 17:28   ` Andreas Dilger
2003-02-09 10:08     ` Stephan van Hienen
2003-02-09 10:32       ` Stephan van Hienen
2003-02-09 20:08       ` Peter Chubb
2003-02-10 11:28         ` Stephan van Hienen
2003-02-09 20:31       ` Andreas Dilger
2003-02-10 12:01         ` Stephan van Hienen
     [not found]           ` <3E479CC7.B170D5C7@aitel.hist.no>
2003-02-11 16:14             ` Re:2TB+ fs ext3 (was fsck out of memory) Stephan van Hienen
2003-02-10 22:44       ` [Ext2-devel] Re: fsck out of memory Stephen C. Tweedie
2003-02-11 13:11         ` Stephan van Hienen
2003-02-11 14:33           ` Stephen C. Tweedie
     [not found]             ` <1044993857.6640.7.camel@plokta.s8.com>
2003-02-11 20:32               ` Re:2TB+ fs ext3 (was fsck out of memory) Stephan van Hienen
2003-02-07 17:24 ` fsck out of memory Andreas Dilger
     [not found] <Pine.LNX.4.33.0302071637050.11484-100000@nooks.wimpunk.com>
2003-02-07 15:50 ` kernel
2003-02-07 16:09   ` Wim Vinckier
2003-02-07 16:15     ` Stephan van Hienen
2003-02-07 16:20       ` Wim Vinckier
2003-02-07 17:08         ` Stephan van Hienen
2003-02-11  2:53 Marco C. Mason

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=Pine.LNX.4.53.0302071555110.718@ddx.a2000.nu \
    --to=kernel@ddx.a2000.nu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@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®