Hello Nab,
Hello Ted,
> > [ 15.663575] EXT4: jbd2_journal_dirty_metadata failed: handle type 5 started at line 244, credits 29/30, errcode -30
> > [ 15.673927] EXT4: jbd2_journal_dirty_metadata failed: handle type 5 started at line 244, credits 29/30, errcode -30[ 15.684549] EXT4-fs error (device sda1) in ext4_free_blocks:4869: Journal has aborted
> > [ 15.693048] EXT4-fs error (device sda1) in ext4_reserve_inode_write:4889: Journal has aborted
> > [ 15.701779] EXT4-fs error (device sda1) in ext4_reserve_inode_write:4889: Journal has aborted
> > [ 15.710477] EXT4-fs error (device sda1) in ext4_ext_remove_space:3019: Journal has aborted
> > [ 15.718916] EXT4-fs error (device sda1) in ext4_ext_truncate:4663: Journal has aborted
> > [ 15.726963] EXT4-fs error (device sda1) in ext4_reserve_inode_write:4889: Journal has aborted
> > [....] Cleaning [ 15.735669] EXT4-fs error (device sda1) in ext4_truncate:3796: Journal has aborted
> > up temporary fil[ 15.749971] EXT4-fs error (device sda1) in ext4_reserve_inode_write:4889: Journal has aborted
> > es...[ 15.759923] EXT4-fs error (device sda1) in ext4_orphan_del:2707: Journal has aborted
> Mmmm, I don't think a simple NULL pointer dereference in the target
> would generate memory corruption in ext4.. Just to confirm, are the
> target LUNs on a different filesystem than the root device..?
I have targets LUNs on the root file system and on another filesystem. I
leave the system as it is in case Ted wants to do some post mortem
analysis. If I don't hear back until after the weekend, I'll reinstall
it.
Cheers,
Thomas
--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
