ext3: unwelcome journal abort

[Jonathan Corbet]

Twice now I've gotten the following with 2.6.28-rc3:

Nov 26 00:15:49 bike kernel: [282457.819704] __log_wait_for_space: no transactions
Nov 26 00:15:49 bike kernel: [282457.819707] Aborting journal on device sda6.
Nov 26 00:15:49 bike kernel: [282457.820824] ext3_abort called.
Nov 26 00:15:49 bike kernel: [282457.820829] EXT3-fs error (device sda6): ext3_journal_start_sb: Detected aborted journal
Nov 26 00:15:49 bike kernel: [282457.820832] Remounting filesystem read-only
Nov 26 00:15:49 bike kernel: [282457.905000] __journal_remove_journal_head: freeing b_committed_data
Nov 26 00:15:49 bike kernel: [282457.905010] __journal_remove_journal_head: freeing b_committed_data
Nov 26 00:15:49 bike kernel: [282457.905273] __journal_remove_journal_head: freeing b_committed_data
Nov 26 00:15:49 bike kernel: [282457.905276] __journal_remove_journal_head: freeing b_committed_data
Nov 26 00:15:49 bike kernel: [282457.905288] __journal_remove_journal_head: freeing b_committed_data
Nov 26 00:15:49 bike kernel: [282457.905298] __journal_remove_journal_head: freeing b_committed_data

Both times, it has happened in the middle of the night; I just find
my /home partition mounted read-only in the morning.  And that, in
turn, makes keeping up with linux-kernel really hard.

I'm pulling the system up to -rc6 now, will yell if it happens again.
Is there anything else I can be looking at in the mean time?

Thanks,

jon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/