On 2024-10-28 10:53, Felix Miata wrote:
Andrei Borzenkov composed on 2024-10-28 10:23 (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) [ 74.896089] [ T637] ext3 filesystem being mounted at /disks/s131 supports timestamps until 2038-01-19 (0x7fffffff) [ 75.457770] [ T638] ext3 filesystem being mounted at /disks/stwt supports timestamps until 2038-01-19 (0x7fffffff) [ 75.507264] [ T634] ext3 filesystem being mounted at /disks/s123 supports timestamps until 2038-01-19 (0x7fffffff) [ 77.426041] [ T654] ext3 filesystem being mounted at /disks/s132 supports timestamps until 2038-01-19 (0x7fffffff) [ 85.148371] [ T700] ext3 filesystem being mounted at /home supports timestamps until 2038-01-19 (0x7fffffff) [ 91.470229] [ T706] ext3 filesystem being mounted at /pub supports timestamps until 2038-01-19 (0x7fffffff) [ 94.088198] [ T711] ext3 filesystem being mounted at /usr/local supports timestamps until 2038-01-19 (0x7fffffff) #
That does not answer my question. Explain how any of these options is related to timestamps. You must have had some reasons to use them.
It's basically the same thing as the Y2K problem was. Weren't you alive then? What "options" are you referring to? I don't understand why you're asking any question. Some, including me, commonly arrange by date operating with groups of files. Files from before the rollover point on filesystems not supporting dates correctly can't be correctly sorted by date mixed with files from after rollover, or show all dates correctly after 0xfffffff rollover point. The question "when was this file last written" won't be answered correctly for writes from before the rollover.
I understand that you would want to upgrade ext2,3 to ext4. But what is not clear is why you use those options on tune2fs. What do they do related to this problem. I have googled and found a document: https://linuxtiwary.com/2016/02/04/how-to-convert-ext3-file-system-to-ext4-w... How to convert ext3 file system to ext4 without any data loss This tutorial is all about how to convert an ext3 file system in linux to an ext4 file system without having any loss in data.You can also say that this article is about file system upgradation in linux without any data loss. Whenever you need to upgrade your linux file system from ext3 to ext4 you can upgrade it very easily without losing your data. Here in this article i have mentioned step wise method to convert an ext3 file system to ext4 file system without any loss in data. And what they do is precissely: #tune2fs -O extents,uninit_bg,dir_index /dev/sda5 #fsck -pf /dev/sda5 #e2fsck -f /dev/sda5 #mount -t ext4 /dev/sda5 /new Still no explanation on how those cryptic options do the conversion from ext3 to ext4. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)