public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@kernel.org
Subject: [Bug 198187] New: jbd2_log_wait_commit hangs
Date: Mon, 18 Dec 2017 12:56:48 +0000	[thread overview]
Message-ID: <bug-198187-13602@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 198187
           Summary: jbd2_log_wait_commit hangs
           Product: File System
           Version: 2.5
    Kernel Version: >=4.13
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: ext4
          Assignee: fs_ext4@kernel-bugs.osdl.org
          Reporter: lav@yar.ru
        Regression: No

sometimes, a process stucks in jbd2_log_wait_commit wait state. After that, any
"sync" and probably fsync calls stuck too. The symptom is LA growing to insane
values. On one server the most common stuck process is logrotate in a lxc
container. I could not log in to two other affected servers. Another few
servers at my disposal do not exhibit this behaviour. There is no disk related
messages in the log or dmesg. Nothing suspicious at all in the log. Graceful
reboot hangs too.

The problem started with 4.13.8 and did not occur in 4.12.8.

Here is the dnf history info after which the problem started to occur:
    Erase    kernel-4.12.8-200.fc25.i686              @updates/25
    Install  kernel-4.13.8-100.fc25.i686              @updates/25

kernel downgrade fixes the problem.

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

             reply	other threads:[~2017-12-18 12:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-18 12:56 bugzilla-daemon [this message]
2017-12-18 12:57 ` [Bug 198187] jbd2_log_wait_commit hangs 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

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@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@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