Eric Sesterhenn wrote: >> Eric , >> can you run the test with below patch and see if this makes any >> difference ?. I know we are not fixing any bugs in the below patch. > > ok, i checked out the old version again and applied both patches, > the BUG is gone (no surprise) > In the case where it would have hit the BUG i now get the following message: > > [ 740.400288] Aborting journal on device loop0.
No message before that about *why* it aborted? > [ 740.405032] ext4_abort called. > [ 740.405097] EXT4-fs error (device loop0): ext4_journal_start_sb: Detected > aborted journal > [ 740.405178] Remounting filesystem read-only > [ 740.410974] EXT4-fs error (device loop0) in ext4_ordered_write_end: IO > failure > [ 740.414300] EXT4-fs error (device loop0) in ext4_reserve_inode_write: > Journal has aborted > [ 740.414422] pa cba56990: logic 16, phys. 1953, len 16 > [ 740.414447] EXT4-fs error (device loop0): ext4_mb_release_inode_pa: free > 4, pa_free 3 > [ 740.414548] EXT4-fs error (device loop0) in ext4_mb_free_blocks: Journal > has aborted > > > Greetings, Eric - To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
