On Jun 6, 2020, at 10:45 AM, Reindl Harald <h.reindl@xxxxxxxxxxxxx> wrote: > > are you guys kidding me? > > * create a new vmware vdisk with 512 MB > * kernel 5.7.0, e2fsprogs-1.45.5-1.fc31.x86_64 > * mount the filesystem > > Jun 6 18:37:57 master kernel: ext4 filesystem being mounted at /boot > supports timestamps until 2038 (0x7fffffff) > > https://lore.kernel.org/patchwork/patch/1172334/ Hi Reindl, It isn't clear if your complaint is about the warning message, or the fact that this is an issue with the newly-formatted filesystem? The *issue* of 2038 timestamps has always existed, but the warning message is newly added so that people have time to fix this if necessary. I wonder if it makes sense to add a superblock flag like "yes, I know this is not 2038 compliant, and I don't care"? > ----------------------------- > > this does *not* happen when the vdisk is 768 MB instead just 512 MB > large - what's te point of defaults which lead to warnings like this in > 2020? This is a matter of space usage. Enabling the 64-bit timestamps requires that the filesystem be formatted with 256-byte inodes, since there wasn't enough space in the original 128-byte inodes for the larger timestamps (among other things). That means either 1/2 as many inodes for the filesystem to fit in the same metadata space, or double the amount of metadata usage for the filesystem (reducing free space). The assumption is that smaller filesystems like this are unlikely to be used for storing long-term data, so maximizing the usable space is most important. It is unlikely you will be using the same /boot filesystem in 18 years, and if you are it is even less likely that it is being updated on a regular basis. It is possible to enable the larger inodes for any size filesystem by formatting with "mk2fs -I 256 <other options> <device>". See "man mke2fs" for full details. Cheers, Andreas
Attachment:
signature.asc
Description: Message signed with OpenPGP
