public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 198187] jbd2_log_wait_commit hangs
Date: Wed, 02 Jan 2019 17:22:28 +0000	[thread overview]
Message-ID: <bug-198187-13602-HgwzyGZbil@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198187-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=198187

--- Comment #14 from Jan Kara (jack@suse.cz) ---
Well, the reason for jbd2 thread staying for long in
jbd2_journal_commit_transaction() can be simply a busy disk. So without more
details it's difficult to tell whether you are really facing the same issue. So
which processes are hung, does the hang eventually resolve itself or is reboot
needed? Please provide sysrq-w output from dmesg when the system is hung.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2019-01-02 17:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-18 12:56 [Bug 198187] New: jbd2_log_wait_commit hangs bugzilla-daemon
2017-12-18 12:57 ` [Bug 198187] " bugzilla-daemon
2017-12-18 23:39 ` bugzilla-daemon
2017-12-20  5:35 ` bugzilla-daemon
2017-12-20  5:36 ` bugzilla-daemon
2017-12-20  5:36 ` bugzilla-daemon
2017-12-20  5:40 ` bugzilla-daemon
2018-01-04 16:10 ` bugzilla-daemon
2018-01-18  6:24 ` bugzilla-daemon
2018-01-18 10:05 ` bugzilla-daemon
2018-01-18 10:33 ` bugzilla-daemon
2018-01-23  7:20 ` bugzilla-daemon
2018-01-24 10:02 ` bugzilla-daemon
2018-01-24 10:47 ` bugzilla-daemon
2019-01-02 15:00 ` bugzilla-daemon
2019-01-02 17:22 ` bugzilla-daemon [this message]

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=bug-198187-13602-HgwzyGZbil@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox