From: "Theodore Ts'o" <tytso@mit.edu>
To: Shashidhar Patil <shashidhar.patil@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: jbd2 task hung in jbd2_journal_commit_transaction
Date: Fri, 19 Mar 2021 11:16:53 -0400 [thread overview]
Message-ID: <YFTAZdfbKUsMmb9A@mit.edu> (raw)
In-Reply-To: <CADve3d7gZVP_wzuRFymox9EEU05jbsTGdf=nGOAHeouBuR1jog@mail.gmail.com>
On Thu, Mar 18, 2021 at 12:27:44PM +0530, Shashidhar Patil wrote:
> Hi Theodore,
> I forgot to include two important details , the stack trace of
> loop0 driver and sar output, which clearly nail the problem.
> The losetup with Ubuntu16.05 does not have O_DIRECT support and we
> were not aware of bypassing of journalling if
> O_DIRECT combined with preallocated file scenario.
Which version of the kernel are you using? The use of O_DIRECT for
loop devices requires kernel and losetup support. (Also note that
upstream developers really generally don't pay attention --- or
support --- distribution kernels unless they work for the company for
which you are paying $$$ for support, and Ubuntu 16.05 isn't even a
Long-Term Support distribution.)
My suggestion is to see if you can replicate the problem on a modern
userspace with the latest kernel. And if not, then that's an object
lesson about why using a antediluvian is not a great life choice. :-)
Cheers,
- Ted
next prev parent reply other threads:[~2021-03-19 15:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 8:03 jbd2 task hung in jbd2_journal_commit_transaction Shashidhar Patil
2021-03-12 12:51 ` Theodore Ts'o
2021-03-13 7:59 ` Shashidhar Patil
2021-03-14 3:38 ` Theodore Ts'o
2021-03-17 15:00 ` Shashidhar Patil
2021-03-17 17:05 ` Theodore Ts'o
2021-03-18 6:57 ` Shashidhar Patil
2021-03-19 15:16 ` Theodore Ts'o [this message]
2021-03-22 6:34 ` Shashidhar Patil
2021-03-19 4:39 ` Shashidhar Patil
-- strict thread matches above, loose matches on Subject: below --
2021-02-15 12:06 Shashidhar Patil
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=YFTAZdfbKUsMmb9A@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=shashidhar.patil@gmail.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