On Thu, Jul 17, 2008 at 3:57 PM, Josef Bacik <jbacik@xxxxxxxxxx> wrote: > Can you try this patch out and see if it fixes the problem? I didn't compile > test it, so you may need to tweak somethings, but it should work. Thanks, > > Signed-off-by: Josef Bacik <jbacik@xxxxxxxxxx> Nope, seems to be the same problem: kjournald starting. Commit interval 5 seconds EXT3-fs warning: mounting fs with errors, running e2fsck is recommended EXT3 FS on loop0, internal journal EXT3-fs: mounted filesystem with ordered data mode. EXT3-fs error (device loop0): ext3_free_blocks: Freeing blocks in system zones - Block = 16, count = 1 EXT3-fs error (device loop0): ext3_free_blocks: Freeing blocks in system zones - Block = 32, count = 1 EXT3-fs error (device loop0): ext3_free_blocks: Freeing blocks not in datazone - block = 262144, count = 1 BUG: unable to handle kernel NULL pointer dereference at 0000000c IP: [<c01fd210>] journal_dirty_metadata+0xa0/0x160 Full log at http://folk.uio.no/vegardno/linux/log-1216304953.txt Vegard -- "The animistic metaphor of the bug that maliciously sneaked in while the programmer was not looking is intellectually dishonest as it disguises that the error is the programmer's own creation." -- E. W. Dijkstra, EWD1036 -- 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
