From: "Stephen C. Tweedie" <sct@redhat.com>
To: Duane Griffin <duaneg@dghda.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-ext4@vger.kernel.org, Sami Liedes <sliedes@cc.hut.fi>,
Stephen Tweedie <sct@redhat.com>
Subject: Re: [PATCH] jbd: abort instead of waiting for nonexistent transactions
Date: Tue, 05 Aug 2008 16:50:37 +0100 [thread overview]
Message-ID: <1217951437.3886.36.camel@sisko.scot.localnet> (raw)
In-Reply-To: <1217893895-29165-1-git-send-email-duaneg@dghda.com>
Hi,
On Tue, 2008-08-05 at 00:51 +0100, Duane Griffin wrote:
> The __log_wait_for_space function sits in a loop checkpointing transactions
> until there is sufficient space free in the journal. However, if there are
> no transactions to be processed (e.g. because the free space calculation is
> wrong due to a corrupted filesystem) it will never progress.
>
> Check for space being required when no transactions are outstanding and
> abort the journal instead of endlessly looping.
I'm not sure this is the right fix --- it seems like we're fixing the
symptoms, not the problem.
The journal free space fields are reset in journal_reset() when we load
the journal, so we can't get this situation of j_free being insufficient
on an idle filesystem unless the main journal start/end pointers are
corrupt.
Surely we'd be better off detecting this in the first place at mount
time, not later on during checkpoint?
Cheers,
Stephen
next prev parent reply other threads:[~2008-08-05 15:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 23:51 [PATCH] jbd: abort instead of waiting for nonexistent transactions Duane Griffin
2008-08-04 23:51 ` [PATCH] jbd2: " Duane Griffin
2008-08-05 0:03 ` [PATCH] jbd: " Andrew Morton
2008-08-05 0:41 ` Duane Griffin
2008-08-05 15:50 ` Stephen C. Tweedie [this message]
2008-08-07 0:47 ` Duane Griffin
2008-08-07 15:01 ` Stephen C. Tweedie
-- strict thread matches above, loose matches on Subject: below --
2008-08-05 1:05 Duane Griffin
2008-08-05 1:42 ` Andrew Morton
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=1217951437.3886.36.camel@sisko.scot.localnet \
--to=sct@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=duaneg@dghda.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sliedes@cc.hut.fi \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox