Re: fsync stuck at jbd2_log_wait_commit on NVMe devices

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux