From: Theodore Ts'o <tytso@mit.edu>
To: Roy Yang <roy@cohesity.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Ext4 stuck at wait_transaction_locked
Date: Sat, 27 Aug 2016 09:36:42 -0400 [thread overview]
Message-ID: <20160827133642.4znpf3aprhgbdtwv@thunk.org> (raw)
In-Reply-To: <CAFz9U7TAWtpQPfgG0u=6_jtVUhK5ahPGGnGy6GK8RZ-0XM2pfg@mail.gmail.com>
On Thu, Aug 25, 2016 at 11:52:07PM -0700, Roy Yang wrote:
> I need your help to debug one ext4 issue. We consistently see Ext4
> stuck at wait_transaction_locked after another process is killed by
> cgroup because of oom. We have two processes keeping writing data to
> the same disk, and one was killed because of oom; the other process
> will stall at all I/O operations pretty soon.
You're using an ancient, 3.10-based RHEL 7 kernel:
> Linux sedhaswell04-node-1 3.10.0-327.22.2.el7.cohesity.x86_64 #1 SMP
> Tue Jul 5 12:41:09 PDT 2016 x86_64 x86_64 x86_64 GNU/Linux
As far as I know this bug does not exist in the upstream kernel ---
but the 3.10 kernel was released in June 2013, and since then changes
are the responsibility of Red Hat / CentOS. So you would need to get
support from Red Hat, since they have made a huge number of changes to
the kernel.
If you had given us the stack trace from the task that got OOM-killed,
we might be able to take a quick look, but if you use a distribution
kernel, it is the responsibility of the distribution to support you
--- this is, after all, why they get paid the big bucks. :-)
If you want to you use the latest upstream kernel, we would be much
more likely to help, although of course unlike Red Hat we don't have
any kind of guaranteed response time. For that, you would need to go
find a distribution and pay the aforementioned big bucks. :-)
Cheers,
- Ted
next prev parent reply other threads:[~2016-08-27 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 6:52 Ext4 stuck at wait_transaction_locked Roy Yang
2016-08-27 13:36 ` Theodore Ts'o [this message]
2016-08-27 14:45 ` Roy Yang
2016-08-27 16:14 ` Theodore Ts'o
[not found] ` <CAFz9U7RxRLLB7dK7YtEVY9qWKKnQ-AbwpL0MT98jx3urbafJmA@mail.gmail.com>
2016-08-27 19:02 ` Theodore Ts'o
2016-08-27 20:12 ` Roy Yang
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=20160827133642.4znpf3aprhgbdtwv@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=roy@cohesity.com \
/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;
as well as URLs for NNTP newsgroup(s).