All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ted Ts'o <tytso@mit.edu>
To: Andre Noll <maan@systemlinux.org>
Cc: Andreas Dilger <adilger@dilger.ca>,
	linux-ext4 <linux-ext4@vger.kernel.org>,
	Marcus Hartmann <marcus.hartmann@tuebingen.mpg.de>
Subject: Re: Memory allocation failed, e2fsck: aborted
Date: Thu, 19 Aug 2010 13:16:20 -0400	[thread overview]
Message-ID: <20100819171620.GB3468@thunk.org> (raw)
In-Reply-To: <20100819131017.GV16603@skl-net.de>

On Thu, Aug 19, 2010 at 03:10:17PM +0200, Andre Noll wrote:
> Silly question: Would it be possible to simply mmap a large enough
> file for the data and and use e.g. rbtrees for the lookups? If yes,
> osl [1] could probably be an option. It's very simple but likely too
> slow on inserts to be useful for e2fsprogs.

As I recall, you're on a 32-bit machine, right?  If so, a limitation
you may run into is simply running out of address space.  If it's not
an address space issue, we don't need to mmap anything; you could just
try enabling swap, and use the existing e2fsck code.

(I had assumed you had tried that before suggesting you use the
scratch_files tdb approach....)

					- Ted

  reply	other threads:[~2010-08-19 17:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-18 14:04 Memory allocation failed, e2fsck: aborted Andre Noll
2010-08-18 20:20 ` Andreas Dilger
2010-08-19  0:54   ` Ted Ts'o
2010-08-19 13:10     ` Andre Noll
2010-08-19 17:16       ` Ted Ts'o [this message]
2010-08-20 14:40         ` Andre Noll
2010-08-20 14:36       ` Andre Noll
2010-08-19 13:01   ` Andre Noll
2010-08-19 19:03     ` Andreas Dilger
2010-08-20 12:46       ` Ted Ts'o
2010-08-20 14:39       ` Andre Noll
2010-08-23 15:53         ` [PATCH]: icount: Replace the icount list by a two-level tree Andre Noll
2010-11-01 22:49           ` Mala Iyer
2010-11-01 23:23             ` Andreas Dilger

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=20100819171620.GB3468@thunk.org \
    --to=tytso@mit.edu \
    --cc=adilger@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=maan@systemlinux.org \
    --cc=marcus.hartmann@tuebingen.mpg.de \
    /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.