linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adam Huffman <adam.huffman@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Errors from e2image
Date: Wed, 28 Nov 2012 18:32:24 +0000	[thread overview]
Message-ID: <CAP5prOhNaffwJaPQageP-jvHTccaEKhQCmwqVbMeSwPq-DUodg@mail.gmail.com> (raw)

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
Illegal block number passed to ext2fs_mark_block_bitmap #825307441 for
in-use block map
Illegal block number passed to ext2fs_mark_block_bitmap #825307441 for
in-use block map
Illegal block number passed to ext2fs_mark_block_bitmap #825307441 for
in-use block map
Illegal block number passed to ext2fs_mark_block_bitmap #170996017 for
in-use block map
Illegal block number passed to ext2fs_mark_block_bitmap #825307441 for
in-use block map
Illegal block number passed to ext2fs_mark_block_bitmap #825307441 for
in-use block map
Illegal block number passed to ext2fs_mark_block_bitmap #825307441 for
in-use block map
Illegal block number passed to ext2fs_mark_block_bitmap #825307441 for
in-use block map
Illegal block number passed to ext2fs_mark_block_bitmap #825307402 for
in-use block map
Illegal block number passed to ext2fs_mark_block_bitmap #825307441 for
in-use block map

Is this something I need to leave running for a long time?  I tried it
on the other problematic LV and the command did complete, though the
qcow2 file it produced was empty.

Cheers,
Adam

             reply	other threads:[~2012-11-28 18:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-28 18:32 Adam Huffman [this message]
2012-11-28 21:29 ` Errors from e2image 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=CAP5prOhNaffwJaPQageP-jvHTccaEKhQCmwqVbMeSwPq-DUodg@mail.gmail.com \
    --to=adam.huffman@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --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).