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=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED 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 DA35AC3A5A2 for ; Tue, 3 Sep 2019 19:50:19 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id B5E8A20882 for ; Tue, 3 Sep 2019 19:50:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726763AbfICTuT (ORCPT ); Tue, 3 Sep 2019 15:50:19 -0400 Received: from mail-qt1-f193.google.com ([209.85.160.193]:39398 "EHLO mail-qt1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725939AbfICTuS (ORCPT ); Tue, 3 Sep 2019 15:50:18 -0400 Received: by mail-qt1-f193.google.com with SMTP id n7so21510024qtb.6; Tue, 03 Sep 2019 12:50:17 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VPptNHDgIrbyunwZQp87iOUTMUhTiMYxTTIn/hXA+LU=; b=kM+ot8AL2uMvl03OY7A0/LZA6tHBB19rbVZbrZfhatMbp3bhBNiMvJIs7sXfmVmxdE E8tnnnnLafy65mjSH+WhzTiW63zmq59DnbE7u7HWXY0kM1XjD+oq90ldUl5ka4z45+Gq Pb/YAXazqxUr6LUyWbGHXLRk9YBLc+OpPW44ohX7kHNgM5jmlqkUsbdaBkC4Jhnk/gXX qPTUyDBpHIf63D3wG4V/rqg9SspItxezN8zF+dyT8VbqvNis3J4wj9ENDkiXEd3D0Owa Wr2ehIeexrTYdfPsuFHnWJzH1b3gzEDNDNpw4tGi+iJmaOixSqKU78JJk+pZ4iXsUksS 62Nw== X-Gm-Message-State: APjAAAVJDzUu1PWaVvWmunOiu8uHl4ifa5+w93wyr9FCFwHZe8Ez9x+t 6O06fO+12Ck7eRIJS010F9DKjIof+axEjxyQX8c= X-Google-Smtp-Source: APXvYqwmWvykYLIsIXv/rExQqRH4453QTzFrznyO0uRb5z3SOOF3l6nvFg1g5Nl4d6IaoTvNw7tWKpHG/sajdmkrkk0= X-Received: by 2002:ac8:6b1a:: with SMTP id w26mr11811379qts.304.1567540217416; Tue, 03 Sep 2019 12:50:17 -0700 (PDT) MIME-Version: 1.0 References: <1567523922.5576.57.camel@lca.pw> <1567534549.5576.62.camel@lca.pw> <82F89AEA-994B-44B5-93E7-CD339E4F78F6@dilger.ca> In-Reply-To: <82F89AEA-994B-44B5-93E7-CD339E4F78F6@dilger.ca> From: Arnd Bergmann Date: Tue, 3 Sep 2019 21:50:00 +0200 Message-ID: Subject: Re: "beyond 2038" warnings from loopback mount is noisy To: Andreas Dilger Cc: Qian Cai , Deepa Dinamani , Jeff Layton , Alexander Viro , Linux FS-devel Mailing List , Linux Kernel Mailing List , "Theodore Ts'o" , Ext4 Developers List Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Sep 3, 2019 at 9:39 PM Andreas Dilger wrote: > > On Sep 3, 2019, at 12:15 PM, Qian Cai wrote: > > > > On Tue, 2019-09-03 at 09:36 -0700, Deepa Dinamani wrote: > >> We might also want to consider updating the file system the LTP is > >> being run on here. > > > > It simply format (mkfs.ext4) a loop back device on ext4 with the kernel. > > > > CONFIG_EXT4_FS=m > > # CONFIG_EXT4_USE_FOR_EXT2 is not set > > # CONFIG_EXT4_FS_POSIX_ACL is not set > > # CONFIG_EXT4_FS_SECURITY is not set > > # CONFIG_EXT4_DEBUG is not set > > > > using e2fsprogs-1.44.6. Do you mean people now need to update the kernel to > > enable additional config to avoid the spam of warnings now? > > Strange. The defaults for mkfs.ext4 _should_ default to use options that > allow enough space for the extra timestamps. > > Can you please provide "dumpe2fs -h" output for your filesystem, and the > formatting options that you used when creating this filesystem. According to the man page, "The default inode size is controlled by the mke2fs.conf(5) file. In the mke2fs.conf file shipped with e2fsprogs, the default inode size is 256 bytes for most file systems, except for small file systems where the inode size will be 128 bytes." If this (small file systems) is the problem, then I think we need to do two things: 1. Change the per-inode warning to not warn if the inode size for the file system is less than 256. We already get a mount-time warning in that case. 2. Change the mkfs.ext4 defaults to never pick a 128 byte inode unless the user really wants this (maybe not even then). Arnd