From: Andre Noll <maan@systemlinux.org>
To: Ted Ts'o <tytso@mit.edu>
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: Fri, 20 Aug 2010 16:36:47 +0200 [thread overview]
Message-ID: <20100820143647.GY16603@skl-net.de> (raw)
In-Reply-To: <20100819131017.GV16603@skl-net.de>
[-- Attachment #1: Type: text/plain, Size: 751 bytes --]
On Thu, Aug 19, 15:10, Andre Noll wrote:
> > Something which *might* help (but will take a long time) is to add to
> > your /etc/e2fsck.conf (if you have one; if not create one wiht these
> > contents):
> >
> > [scratch_files]
> > directory = /var/cache/fsck
> >
> > (And then make sure /var/cache/fsck exists.)
>
> Thanks for the hint. It is running for an hour now and I will report
> back tomorrow. ATM, it's at 1% and the two files in /var/cache/fsck
> are ~50M large.
It got much slower: 4.8% after one day. So I cancelled the fsck and
am copying the raw device to a 64bit machine and run fsck there,
as Andreas suggested.
Thanks
Andre
--
The only person who always got his work done by Friday was Robinson Crusoe
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2010-08-20 14:36 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
2010-08-20 14:40 ` Andre Noll
2010-08-20 14:36 ` Andre Noll [this message]
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=20100820143647.GY16603@skl-net.de \
--to=maan@systemlinux.org \
--cc=adilger@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=marcus.hartmann@tuebingen.mpg.de \
--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;
as well as URLs for NNTP newsgroup(s).