Messages in this thread | | | Date | Thu, 30 Oct 2008 22:43:25 +0200 (EET) | From | Meelis Roos <> | Subject | Re: 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 (mroos@linux.ee)
| |