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 -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
