mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephan van Hienen <raid@a2000.nu>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
	ext2-devel@lists.sourceforge.net, "Theodore Ts'o" <tytso@mit.edu>,
	peter@chubb.wattle.id.au, tbm@a2000.nu
Subject: Re: fsck out of memory
Date: Sun, 9 Feb 2003 11:08:44 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.53.0302090953440.1039@ddx.a2000.nu> (raw)
In-Reply-To: <20030207102858.P18636@schatzie.adilger.int>

On Fri, 7 Feb 2003, Andreas Dilger wrote:

> Hmm, I don't think that will be easy...  By default e2fsck will load all
> of the inode blocks into memory (pretty sure at least), and if you have
> 76922880 inodes that is 9.6GB of memory, which you can't allocate from a
> single process on i386 no matter how much swap you have.  2.5GB sounds
> about right for the maximum amount of memory one can allocate.

hmms the data is not critical yet (i was just testing this server)
i really wonder why the crash was there in the first place

thing i found in /var/log/messages :

Feb  7 04:18:15 storage kernel: EXT3-fs error (device md(9,0)):
ext3_new_block:
Allocating block in system zone - block = 536875638
Feb  7 04:18:15 storage kernel: EXT3-fs error (device md(9,0)):
ext3_new_block:
Allocating block in system zone - block = 536875639

doesn't look ok to me (and explains the crash?)

makes me wonder if this can have todo with the lbd (to allow 2TB+ devices)
patch ? or is this something else?
(if it can be related to the lbd patch, i will remove 2 hd's from the
array (but i don't prefer this option))

also for not getting this thing again (that i can't fsck my filesystem)
what are the setting i can use for creating a large filesystem on /dev/md0
? (what is the maximum workable inodes?)

i did this :

mke2fs -j -m 0  -b 4096 -i 4096 -R stride=16


  reply	other threads:[~2003-02-09  9:59 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 [this message]
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.0302090953440.1039@ddx.a2000.nu \
    --to=raid@a2000.nu \
    --cc=adilger@clusterfs.com \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=peter@chubb.wattle.id.au \
    --cc=tbm@a2000.nu \
    --cc=tytso@mit.edu \
    /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®