From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 70153C433DB for ; Fri, 19 Mar 2021 15:17:56 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 4151F61929 for ; Fri, 19 Mar 2021 15:17:56 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230063AbhCSPRY (ORCPT ); Fri, 19 Mar 2021 11:17:24 -0400 Received: from outgoing-auth-1.mit.edu ([18.9.28.11]:50564 "EHLO outgoing.mit.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S229978AbhCSPQ5 (ORCPT ); Fri, 19 Mar 2021 11:16:57 -0400 Received: from cwcc.thunk.org (pool-72-74-133-215.bstnma.fios.verizon.net [72.74.133.215]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 12JFGrIB019344 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 19 Mar 2021 11:16:54 -0400 Received: by cwcc.thunk.org (Postfix, from userid 15806) id 526B815C39CA; Fri, 19 Mar 2021 11:16:53 -0400 (EDT) Date: Fri, 19 Mar 2021 11:16:53 -0400 From: "Theodore Ts'o" To: Shashidhar Patil Cc: linux-ext4@vger.kernel.org Subject: Re: jbd2 task hung in jbd2_journal_commit_transaction Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org 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