linux-ext4 - Re: fsync stuck at jbd2_log_wait

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20150813130953.GA26095@thunk.org>
Date:	Thu, 13 Aug 2015 09:09:53 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Roy Yang <bsdnet@...look.com>
Cc:	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: fsync stuck at jbd2_log_wait_commit on NVMe devices

On Wed, Aug 12, 2015 at 04:34:17PM -0700, Roy Yang wrote:
> Hi Ted, 
> 
>    Appreciate your time, and will get the log from normal work load.
> 
>    BTW, the previous JBD2 log is from the node which is in bad state. 
>   Normal node finish within 3 seconds; while on this node, it takes 10 seconds.

Ah, you didn't say that.

If this is a node in a bad state, and we're not seeing any real delays
from the jbd2 logs, then it sounds very much like the problem is a
hardware issue (or maybe an NVMe device driver issue).  You might want
to use blktrace to see how long the underlying I/O operations are
taking to complete.

						- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html