mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: kernel@ddx.a2000.nu
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: fsck out of memory
Date: Fri, 7 Feb 2003 10:24:42 -0700	[thread overview]
Message-ID: <20030207102442.O18636@schatzie.adilger.int> (raw)
In-Reply-To: <Pine.LNX.4.53.0302071555110.718@ddx.a2000.nu>; from kernel@ddx.a2000.nu on Fri, Feb 07, 2003 at 04:17:35PM +0100

On Feb 07, 2003  16:17 +0100, kernel@ddx.a2000.nu wrote:
> 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).
> 
> I really wonder if there is something wrong with e2fsk ?
> does it really need that much memory ?
> (fsck on 2.2TB /dev/md0)

I don't think many people have run e2fsck on such a large filesystem
before when there are lots of problems.  It is entirely possible that
you need so much memory for such a large filesystem.  I would suggest
creating a larger swap file temporarily (on some other partition) so
that e2fsck can complete.

It _may_ be that e2fsck could reduce memory consumption somewhere (or
enable a "use less memory but run slowly" heuristic, but that isn't
very likely, or if it was it would be very slow.

Regarding the "use fsck.ext3" response - ignore it, it is incorrect.
There is no difference at all between fsck.ext2, fsck.ext3, e2fsck.

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/


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

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-07 15:17 kernel
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 ` Andreas Dilger [this message]
     [not found] <Pine.LNX.4.33.0302071637050.11484-100000@nooks.wimpunk.com>
2003-02-07 15:50 ` fsck out of memory 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=20030207102442.O18636@schatzie.adilger.int \
    --to=adilger@clusterfs.com \
    --cc=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®