From: Alex Lyashkov <shadow@itt.net.ru>
To: Jan Kara <jack@suse.cz>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
Herbert Poetzl <herbert@13thfloor.at>
Subject: [BUG] journal handler reference count breaked and fs deadlocked
Date: Sun, 9 Nov 2003 23:34:00 +0200 [thread overview]
Message-ID: <200311092334.01957.shadow@itt.net.ru> (raw)
Hello All
I try locate what are point where fs deadlocked.
after recompile kernel with debug jbd and set debug level to 100 i log kernel
via serial console
after deadlock - i see in log
==============
journal.c, 581): log_start_commit: JBD: requesting commit 501252/501251
(journal.c, 608): log_wait_commit: JBD: want 501252, j_commit_sequence=501251
(journal.c, 263): kjournald: kjournald wakes
(journal.c, 238): kjournald: commit_sequence=501251, commit_request=501252
(journal.c, 242): kjournald: OK, requests differ
(commit.c, 81): journal_commit_transaction: JBD: starting commit of
transaction 501252
(commit.c, 87): journal_commit_transaction: wait updates.......
(transaction.c, 567): do_get_write_access: buffer_head c79f2e70, force_copy 0
(revoke.c, 375): journal_cancel_revoke: journal_head c79f2e70, cancelling
revoke
(transaction.c, 567): do_get_write_access: buffer_head c79f2e70, force_copy 0
(revoke.c, 375): journal_cancel_revoke: journal_head c79f2e70, cancelling
revoke
(transaction.c, 1104): journal_dirty_metadata: journal_head c79f2e70
(transaction.c, 1392): journal_stop: h_ref 2 -> 1
==============
i think it`s reason fs deadlocked, because wait query not be waked :-\
if i right - it very big problem on ext3..
other logs\infos can be created after request....
--
With best regards,
Alex
next reply other threads:[~2003-11-09 21:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-09 21:34 Alex Lyashkov [this message]
2003-11-10 9:12 ` [BUG] journal handler reference count breaked and fs deadlocked Alex Tomas
2003-11-10 9:55 ` Alex Lyashkov
2003-11-10 11:13 ` Jan Kara
2003-11-10 11:48 ` Alex Lyashkov
2003-11-10 11:50 ` Jan Kara
2003-11-10 13:07 ` Alex Lyashkov
2003-11-10 16:07 ` Alex Lyashkov
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=200311092334.01957.shadow@itt.net.ru \
--to=shadow@itt.net.ru \
--cc=akpm@osdl.org \
--cc=herbert@13thfloor.at \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.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 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.