Hi Andrea,
> > ok, now it's clear what the problem is. there are inuse-dirty inodes
> > that triggers a deadlock in the schedule-capable
> > try_to_sync_unused_inodes of 2.4.20rc2aa1 (that avoided me to backout an
> > otherwise corrupt lowlatency fix). It can trigger only in UP,
> > in SMP the other cpu can always run kupdate that will flush all dirty
> > inodes, so it would lockup one cpu as worse for 2.5 sec, this is
> > probably why I couldn't reproduce it, I assume all of you reproducing
> > the deadlock were running on an UP machine (doesn't matter if the kernel
> Correct (for me anyways).
ok, deadlock is gone, instead I have EXT3-fs corruption (non data=journal
mode, just ordered) like this:
Dec 3 00:25:39 codeman kernel: EXT3-fs error (device ide0(3,9)):
ext3_free_blocks: Freeing blocks not in datazone - block = 1530182
, count = 1
Dec 3 00:25:39 codeman kernel: Aborting journal on device ide0(3,9).
Dec 3 00:25:39 codeman kernel: ext3_free_blocks: aborting transaction:
Journal has aborted in __ext3_journal_get_undo_access<2>EXT3
-fs error (device ide0(3,9)) in ext3_free_blocks: Journal has aborted
Dec 3 00:25:39 codeman kernel: ext3_reserve_inode_write: aborting
transaction: Journal has aborted in __ext3_journal_get_write_acce
ss<2>EXT3-fs error (device ide0(3,9)) in ext3_reserve_inode_write: Journal has
aborted
Dec 3 00:25:39 codeman kernel: EXT3-fs error (device ide0(3,9)) in
ext3_truncate: Journal has aborted
Dec 3 00:25:39 codeman kernel: ext3_reserve_inode_write: aborting
transaction: Journal has aborted in __ext3_journal_get_write_acce
ss<2>EXT3-fs error (device ide0(3,9)) in ext3_reserve_inode_write: Journal has
aborted
Dec 3 00:25:39 codeman kernel: EXT3-fs error (device ide0(3,9)) in
ext3_orphan_del: Journal has aborted
Dec 3 00:25:39 codeman kernel: ext3_reserve_inode_write: aborting
transaction: Journal has aborted in __ext3_journal_get_write_acce
ss<2>EXT3-fs error (device ide0(3,9)) in ext3_reserve_inode_write: Journal has
aborted
Dec 3 00:25:39 codeman kernel: EXT3-fs error (device ide0(3,9)) in
ext3_delete_inode: Journal has aborted
Dec 3 00:25:39 codeman kernel: ext3_abort called.
Dec 3 00:25:39 codeman kernel: EXT3-fs abort (device ide0(3,9)):
ext3_journal_start: Detected aborted journal
Dec 3 00:25:39 codeman kernel: Remounting filesystem read-only
Dec 3 00:25:39 codeman kernel: EXT3-fs error (device ide0(3,9)) in
start_transaction: Journal has aborted
BTW: UP, non-SMP.
ciao, Marc
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Dec 07 2002 - 22:00:15 EST