From: Theodore Ts'o <tytso@mit.edu>
To: Justin Brown <justin.brown@fandingo.org>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Fsck.ext4: Memory Allocation Failed
Date: Mon, 31 Mar 2014 22:22:31 -0400 [thread overview]
Message-ID: <20140401022231.GC4911@thunk.org> (raw)
In-Reply-To: <CAKZK7uwTp2cMoWLiWZSa5UfZ2dCxRaB7KLZ0PtVVSqimp=tLJA@mail.gmail.com>
On Mon, Mar 31, 2014 at 03:49:29PM -0500, Justin Brown wrote:
> Pass 1: Checking inodes, blocks, and sizes
> Inode 14109880 has illegal block(s). Clear? yes
>
> Illegal block #0 (3925875673) in inode 14109880. CLEARED.
> Illegal block #2 (85326080) in inode 14109880. CLEARED.
> Illegal block #3 (2516589529) in inode 14109880. CLEARED.
> Illegal block #5 (3641317099) in inode 14109880. CLEARED.
> Illegal block #6 (394723355) in inode 14109880. CLEARED.
> Illegal block #7 (2986344453) in inode 14109880. CLEARED.
> Illegal block #8 (3640903191) in inode 14109880. CLEARED.
> Illegal block #9 (463536155) in inode 14109880. CLEARED.
> Illegal block #11 (1275199487) in inode 14109880. CLEARED.
> Illegal double indirect block (2181366192) in inode 14109880. CLEARED.
> Illegal block #563086348 (4294967295) in inode 14109880. CLEARED.
> Error storing directory block information (inode=14109880, block=0,
> num=471166008): Memory allocation failed
Sorry, this is a bug in e2fsck; we should handle this kind of
corrupted inode better.
The quick workaround is this:
debugfs -w -R "clri <14109880>" /dev/vg/root
This will zap the contents of the offending inode, since it's been
overwritten with garbage; unfortunately, it was garbage which was
causing e2fsck to try to allocate too much memory, and then fail.
- Ted
next prev parent reply other threads:[~2014-04-01 2:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 20:49 Fsck.ext4: Memory Allocation Failed Justin Brown
2014-04-01 2:22 ` Theodore Ts'o [this message]
2014-04-01 20:15 ` Justin Brown
2014-04-01 20:36 ` Theodore Ts'o
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=20140401022231.GC4911@thunk.org \
--to=tytso@mit.edu \
--cc=justin.brown@fandingo.org \
--cc=linux-ext4@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 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.