From: Theodore Tso <tytso@mit.edu>
To: Meelis Roos <mroos@linux.ee>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: ext3 __log_wait_for_space: no transactions
Date: Thu, 30 Oct 2008 10:21:03 -0400 [thread overview]
Message-ID: <20081030142103.GA14744@mit.edu> (raw)
In-Reply-To: <Pine.SOC.4.64.0810301147310.10441@math.ut.ee>
On Thu, Oct 30, 2008 at 11:49:34AM +0200, Meelis Roos wrote:
> I get this problem nightly on 2.6.28-rc2-* kernels on a generic
> Celeron 900/Intel 815/PATA/ext3 system.
>
> __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
If it's happening nightly, I assume it's because some cron job is
going off; it would be interesting to see what was going on at that time.
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.
- Ted
next prev parent reply other threads:[~2008-10-30 14:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 9:49 ext3 __log_wait_for_space: no transactions Meelis Roos
2008-10-30 14:21 ` Theodore Tso [this message]
2008-10-30 20:43 ` Meelis Roos
2008-10-31 14:07 ` Theodore Tso
2008-10-31 14:45 ` Meelis Roos
2008-10-31 13:39 ` Meelis Roos
2008-11-01 6:54 ` Andrew Morton
2008-11-01 8:56 ` Simon Arlott
2008-11-01 8:59 ` Meelis Roos
2008-11-01 16:38 ` Theodore Tso
2008-11-01 17:10 ` Theodore Tso
2008-11-01 20:21 ` Bartlomiej Zolnierkiewicz
2008-11-04 14:50 ` Theodore Tso
2008-11-04 14:54 ` Meelis Roos
2008-11-04 17:48 ` Bartlomiej Zolnierkiewicz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081030142103.GA14744@mit.edu \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.