Messages in this thread | | | Date | Fri, 31 Oct 2008 10:07:42 -0400 | From | Theodore Tso <> | Subject | Re: ext3 __log_wait_for_space: no transactions |
| |
On Thu, Oct 30, 2008 at 10:43:25PM +0200, Meelis Roos wrote: > > > __log_wait_for_space: no transactions > > > Aborting journal on device sda3. > > > ext3_abort called. > > > EXT3-fs error (device sda3): ext3_journal_start_sb: Detected aborted journal > > > Remounting filesystem read-only > > > > How big is your journal? What does this report? > > > > dumpe2fs -h /dev/sda3| grep Journal > > dumpe2fs 1.41.3 (12-Oct-2008) > Journal inode: 8 > Journal backup: inode blocks > Journal size: 32M
You'll almost certainly get much better performance if you increase your journal size. I should make the crash go away, too, although I would like to figure out what is going on so we can fix it.
But, if you're tired of your machine crashing, it should be possible to deal with the problem by umounting the filesystem (assuming this is not your root filesystem; if it is, you'll have to boot into a rescue CD) and doing:
tune2fs -O ^has_journal /dev/sda3 tune2fs -O has_journal -J size=128 /dev/sda3
In the meantime, you say this happens nightly. Can you take a look at the time when it normally crashes and see if you can correlate it to some cron job activity? Maybe that will be a hint as to what is triggering it.
Thanks,
- Ted
| |