linux-kernel - Re: "beyond 2038" warnings from loopback mount is noisy

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <31a671ea-a00b-37da-5f30-558c3ab6d690@thelounge.net>
Date:   Tue, 3 Sep 2019 23:52:18 +0200
From:   Reindl Harald <h.reindl@...lounge.net>
To:     "Theodore Y. Ts'o" <tytso@....edu>,
        Deepa Dinamani <deepa.kernel@...il.com>
Cc:     Qian Cai <cai@....pw>, Jeff Layton <jlayton@...nel.org>,
        Alexander Viro <viro@...iv.linux.org.uk>,
        Linux FS-devel Mailing List <linux-fsdevel@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Ext4 Developers List <linux-ext4@...r.kernel.org>,
        Andreas Dilger <adilger.kernel@...ger.ca>,
        Arnd Bergmann <arnd@...db.de>
Subject: Re: "beyond 2038" warnings from loopback mount is noisy



Am 03.09.19 um 23:17 schrieb Theodore Y. Ts'o:
> I know of a truly vast number of servers in production all over the
> world which are using 128 byte inodes, and spamming the inodes at the
> maximum rate limit is a really bad idea.  This includes at some major
> cloud data centers where the life of individual servers in their data
> centers is well understood (they're not going to last until 2038)

well, i didn't ask the Fedora installer for 128 byte indoes in 2008 on
the 500 MB small /boot while the 6 GB rootfs has 256 byte while this
setups are surely targeted to last longer than 2038 until someone kills
Fedora with all the shiny new stuff nobody needs

but yes, don't start to spam me about it

[root@...akis:~]$ tune2fs -l /dev/sda1
tune2fs 1.44.6 (5-Mar-2019)
Filesystem volume name:   boot
Last mounted on:          /boot
Filesystem UUID:          b834776d-69d1-49c6-97c1-d6d758a438f0
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index
filetype needs_recovery extent sparse_super uninit_bg
Filesystem flags:         signed_directory_hash
Default mount options:    (none)
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              130560
Block count:              521215
Reserved block count:     2
Free blocks:              455376
Free inodes:              130216
First block:              1
Block size:               1024
Fragment size:            1024
Reserved GDT blocks:      256
Blocks per group:         8192
Fragments per group:      8192
Inodes per group:         2040
Inode blocks per group:   255
Filesystem created:       Mon Aug 18 06:48:14 2008
Last mount time:          Sat Aug 17 02:49:03 2019
Last write time:          Tue Sep  3 02:03:44 2019
Mount count:              19
Maximum mount count:      30
Last checked:             Sat Dec 15 04:36:27 2018
Check interval:           31104000 (12 months)
Next check after:         Tue Dec 10 04:36:27 2019
Lifetime writes:          64 GB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               128
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      2cc862b9-dc3e-4707-b6ed-9a7fe724dd2e
Journal backup:           inode blocks