From: Jan Kara <jack@suse.cz>
To: John Madden <weez@freelists.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.11, nfsd, log_do_checkpoint()
Date: Mon, 4 Apr 2005 11:38:02 +0200 [thread overview]
Message-ID: <20050404093802.GC20219@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <200504011927.19030.weez@freelists.org>
[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]
Hello!
> I woke up to a mostly-dead PE1850 this morning:
>
> Message from syslogd@storage at Fri Apr 1 06:19:14 2005 ...
> storage kernel: Assertion failure in log_do_checkpoint() at
> fs/jbd/checkpoint.c:365: "drop_count != 0 || cleanup_ret != 0"
>
> Message from syslogd@storage at Fri Apr 1 06:19:14 2005 ...
> storage kernel: invalid operand: 0000 [1] SMP
>
> Full error:
>
> Assertion failure in log_do_checkpoint() at fs/jbd/checkpoint.c:365:
> "drop_count != 0 || cleanup_ret != 0"
Could you try running a kernel with the attached patch? Are you able to
reproduce the problem even with the patch?
> ----------- [cut here ] --------- [please bite here ] ---------
> Kernel BUG at checkpoint:365
> invalid operand: 0000 [1] SMP
> CPU 1
> Modules linked in:
> Pid: 212, comm: nfsd Not tainted 2.6.11-rc5
<snip>
> nfsd was serving out a pretty heavily-used (2.5-million page web site) ext3
> partition on the 1850's built-in LSI/MPT controller. I'm able to duplicate
> this somewhat consistently by putting nfsd under heavy load (say, by deleting
> 20,000 files from a directory).
>
> (Please Cc me on replies, I'm not subscribed.)
Honza
--
Jan Kara <jack@suse.cz>
SuSE CR Labs
[-- Attachment #2: ext3-release-race.patch --]
[-- Type: text/plain, Size: 1616 bytes --]
linux-2.6.11-ext3-release-race.patch:
transaction.c | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
--- NEW FILE linux-2.6.11-ext3-release-race.patch ---
--- linux-2.6.9/fs/jbd/transaction.c.=K0002=.orig
+++ linux-2.6.9/fs/jbd/transaction.c
@@ -1812,10 +1812,10 @@ static int journal_unmap_buffer(journal_
JBUFFER_TRACE(jh, "checkpointed: add to BJ_Forget");
ret = __dispose_buffer(jh,
journal->j_running_transaction);
+ journal_put_journal_head(jh);
spin_unlock(&journal->j_list_lock);
jbd_unlock_bh_state(bh);
spin_unlock(&journal->j_state_lock);
- journal_put_journal_head(jh);
return ret;
} else {
/* There is no currently-running transaction. So the
@@ -1826,10 +1826,10 @@ static int journal_unmap_buffer(journal_
JBUFFER_TRACE(jh, "give to committing trans");
ret = __dispose_buffer(jh,
journal->j_committing_transaction);
+ journal_put_journal_head(jh);
spin_unlock(&journal->j_list_lock);
jbd_unlock_bh_state(bh);
spin_unlock(&journal->j_state_lock);
- journal_put_journal_head(jh);
return ret;
} else {
/* The orphan record's transaction has
@@ -1850,10 +1850,10 @@ static int journal_unmap_buffer(journal_
journal->j_running_transaction);
jh->b_next_transaction = NULL;
}
+ journal_put_journal_head(jh);
spin_unlock(&journal->j_list_lock);
jbd_unlock_bh_state(bh);
spin_unlock(&journal->j_state_lock);
- journal_put_journal_head(jh);
return 0;
} else {
/* Good, the buffer belongs to the running transaction.
next prev parent reply other threads:[~2005-04-04 9:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-02 0:27 John Madden
2005-04-04 9:38 ` Jan Kara [this message]
2005-04-04 12:55 ` John Madden
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=20050404093802.GC20219@atrey.karlin.mff.cuni.cz \
--to=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=weez@freelists.org \
/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
all inboxes | Powered by JetHome®