Andrei Borzenkov composed on 2024-10-28 21:34 (UTC+0300):
Felix Miata wrote:
Andrei Borzenkov composed on 2024-10-28 09:38 (UTC+0300):
Felix Miata wrote:
I'm in process of eliminating EXT2 & EXT3 filesystems from old computers, due to the year 2038 date problem that might arrive before my termination. Using:
tune2fs -O extents,uninit_bg,dir_index /dev/sdb1
How is all of this related to the year 2038 or timestamps in general?
# dmesg | egrep '2038|pports' … [ 70.533547] [ T674] ext2 filesystem being mounted at /disks/boot supports timestamps until 2038-01-19 (0x7fffffff)
This message was added in the kernel 5.4. Nowhere in your post did you mention you were running this or newer version. You only talked about kernel 2.6.22.19 which could not emit this message at all.
Somewhere in this thread I explained that 10.2 kernels were not supporting ext4 /, to that I was needing to boot something else and chroot to do things like running 10.2's mkinitrd. To answer your question, I booted something else capable of providing timestamp support messages. It looks like the something else I selected was probably Fedora 28 or 29 or Mageia 6, rather than Debian, TW or 11.4.
[ 74.896089] [ T637] ext3 filesystem being mounted at /disks/s131 supports timestamps until 2038-01-19 (0x7fffffff)
Kernel 5.4 does not have ext3 driver, it has ext4 driver which can also mount ext3 filesystem. ext4 driver will set max timestamp depending on the inode size. It needs to be at least 256 bytes. Setting options with tune2fs does *not* change existing inode size.
According to Manfred's thread response, it appears tune2fs *can* change existing inode size (e.g. from 128 to 256). -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata