[lkml]   [2008]   [Oct]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: ext3 __log_wait_for_space: no transactions
> > __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

> The other thing that would be useful would be to replace the call to
> journal_abort() in __log_wait_for_space() in fs/jbd/checkpoint.c with
> a BUG(), so we can get a stack backtrace and see what filesystem
> operation was calling start_this_handle() (which in turn was calling
> __log_wait_for_space) that is triggering this bug.

Will try.

Meelis Roos (

 \ /
  Last update: 2008-10-30 21:45    [W:0.075 / U:38.324 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site