From: Theodore Ts'o <tytso@mit.edu>
To: Adam Huffman <adam.huffman@gmail.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: Errors from e2image
Date: Wed, 28 Nov 2012 16:29:03 -0500 [thread overview]
Message-ID: <20121128212903.GB30650@thunk.org> (raw)
In-Reply-To: <CAP5prOhNaffwJaPQageP-jvHTccaEKhQCmwqVbMeSwPq-DUodg@mail.gmail.com>
On Wed, Nov 28, 2012 at 06:32:24PM +0000, Adam Huffman wrote:
> Hello again
>
> I've just run e2image, as you suggested and it doesn't look like it's
> ever going to complete.
>
> There are lots of errors on the console like:
>
> Illegal block number passed to ext2fs_mark_block_bitmap #822751537 for
> in-use block map
Hmmm.., can you send me the *complete* output of e2fsck -n on the file system image?
This is a very basic error caused by illegal block numbers in an inode
extent map (or indirect block). E2fsck should have reported this, and
fixing this is not hard. Yet nothing you sent me showed anything like
that --- but you've only sent me excerpts, and not the full e2fsck
output.....
> Is this something I need to leave running for a long time?
How big is your file system? It shouldn't take that long, but the
illegal block numbers should not caused it to get it stuck in a loop.
> I tried it
> on the other problematic LV and the command did complete, though the
> qcow2 file it produced was empty.
Now *that's* just weird. Just to be sure... can you try reinstalling
the e2fsprogs package on your system? I'm wondering if the shared
libraries have gotten subtly corrupted somehow.... what you are
reporting just doesn't make any sense....
- Ted
prev parent reply other threads:[~2012-11-28 21:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 18:32 Errors from e2image Adam Huffman
2012-11-28 21:29 ` Theodore Ts'o [this message]
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=20121128212903.GB30650@thunk.org \
--to=tytso@mit.edu \
--cc=adam.huffman@gmail.com \
--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 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).