LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-10-2021, 04:45 PM   #1
Jeebizz
Senior Member
 
Registered: May 2004
Distribution: Slackware14.2 64-Bit Desktop, Devuan 2.0 ASCII Toshiba Satellite Notebook
Posts: 3,191

Rep: Reputation: 938Reputation: 938Reputation: 938Reputation: 938Reputation: 938Reputation: 938Reputation: 938Reputation: 938
Question XFS and 2038 down the road


So I keep seeing this each time I boot up, I do not really think much of it but lately it has been making me wonder. What are the devs of XFS doing about this? Does it really matter though? Are invalid timestamps going to keep me from accessing my data, or should I just ignore this?

Code:
[11.435672] xfs filesystem being mounted at /home supports timestamps until 2038 (0x7fffffff)
 
Old 05-10-2021, 05:27 PM   #2
LuckyCyborg
Senior Member
 
Registered: Mar 2010
Posts: 1,371

Rep: Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139
Quote:
Originally Posted by Jeebizz View Post
So I keep seeing this each time I boot up, I do not really think much of it but lately it has been making me wonder. What are the devs of XFS doing about this? Does it really matter though? Are invalid timestamps going to keep me from accessing my data, or should I just ignore this?

Code:
[11.435672] xfs filesystem being mounted at /home supports timestamps until 2038 (0x7fffffff)
I remember that long time ago, while 2005, I had a computer affected by Y2K. And wasn't connected to Internet.

Basically, the issue manifested that every time I needed to set the clock and date, and on the next startup the date returned on 1990. In the end, I have invented a script which added the missing years to date, at boot time.

So, I guess that if nothing changes on the next 15 years with your XFS, on 2039 you will save a file, and it will get a timestamp around 1986.

That would probably break the make job, which is based on files timestamp, from what I known - your files will be always older than dirt.

I have no idea if something else will break too, but I am almost certain that make would not like this.

Last edited by LuckyCyborg; 05-10-2021 at 05:30 PM.
 
Old 05-10-2021, 05:32 PM   #3
michaelk
Moderator
 
Registered: Aug 2002
Posts: 21,491

Rep: Reputation: 4106Reputation: 4106Reputation: 4106Reputation: 4106Reputation: 4106Reputation: 4106Reputation: 4106Reputation: 4106Reputation: 4106Reputation: 4106Reputation: 4106
A quick search show the short term fix is in the 5.1 kernel which moves the new date to 2486.

https://m.slashdot.org/story/377146
 
2 members found this post helpful.
Old 05-10-2021, 05:40 PM   #4
LuckyCyborg
Senior Member
 
Registered: Mar 2010
Posts: 1,371

Rep: Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139
Quote:
Originally Posted by michaelk View Post
A quick search show the short term fix is in the 5.1 kernel which moves the new date to 2486.

https://m.slashdot.org/story/377146
BUT, probably it talks about fresh formatted partitions. We already are on kernel 5.10 then the kernel shouldn't be a problem.

However, from what I known, is about a slightly different filesystem, as how it's stored on disk. Just like they did also with EXT[234]

So, probably our OP have a task to do on the next 15 years: to backup his /home and do a fresh format. Assuming that the hard drive will survive another 15 years.
 
Old 05-10-2021, 05:42 PM   #5
Jeebizz
Senior Member
 
Registered: May 2004
Distribution: Slackware14.2 64-Bit Desktop, Devuan 2.0 ASCII Toshiba Satellite Notebook
Posts: 3,191

Original Poster
Rep: Reputation: 938Reputation: 938Reputation: 938Reputation: 938Reputation: 938Reputation: 938Reputation: 938Reputation: 938
Quote:
Originally Posted by LuckyCyborg View Post
I remember that long time ago, while 2005, I had a computer affected by Y2K. And wasn't connected to Internet.

Basically, the issue manifested that every time I needed to set the clock and date, and on the next startup the date returned on 1990. In the end, I have invented a script which added the missing years to date, at boot time.

So, I guess that if nothing changes on the next 15 years with your XFS, on 2039 you will save a file, and it will get a timestamp around 1986.

That would probably break the make job, which is based on files timestamp, from what I known - your files will be always older than dirt.

I have no idea if something else will break too, but I am almost certain that make would not like this.
Well I use XFS for / and /home and my external HD (backup) is formatted as XFS as well. I am just wondering if I need to make plans to switch to another FS when the time comes or... I honestly don't know .


Quote:
Originally Posted by michaelk View Post
A quick search show the short term fix is in the 5.1 kernel which moves the new date to 2486.

https://m.slashdot.org/story/377146
So just kicking the can down the line I guess, and in another note running --Current produces this very message as well - so I would have thought this fix would have been applied for 5.10, apparently not.
 
Old 05-10-2021, 06:21 PM   #6
rkelsen
Senior Member
 
Registered: Sep 2004
Distribution: slackware
Posts: 2,936
Blog Entries: 3

Rep: Reputation: 1144Reputation: 1144Reputation: 1144Reputation: 1144Reputation: 1144Reputation: 1144Reputation: 1144Reputation: 1144Reputation: 1144
Quote:
Originally Posted by michaelk View Post
A quick search show the short term fix is in the 5.1 kernel which moves the new date to 2486.
That's just short term thinking.
 
Old 05-10-2021, 07:25 PM   #7
jwoithe
LQ Newbie
 
Registered: Oct 2019
Posts: 27

Rep: Reputation: Disabled
While kernel 5.10 includes support which pushes XFS timestamps out to 2486, the feature is not enabled by default by mkfs.xfs to preserve backwards compatibility. Such compatibility is important if a device is moved between systems which don't all have a 5.10 (or later) kernel. As a result, even when running the 5.10 kernel, a "mkfs.xfs" will create a filesystem whose timestamps are limited to 2038. This is why the 2038 message is still seen on XFS filesystems created using Slackware/Slackware64 current. To force the use of the extended timestamp range, pass "-m bigtime=1" to mkfs.xfs:
Code:
mkfs.xfs -m bigtime=1 /dev/...
Apparently under the 5.11 kernel it's possible to convert an unmounted XFS filesystem to use the extended timestamp range:
Code:
xfs_admin -O bigtime=1 /dev/...
This is handy since it means that existing filesystems can be migrated to the new timestamp range once it's certain they no longer need to be used on pre-5.10 systems.
 
4 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Road Redemption a spiritual successor to Road Rash for Linux! LXer Syndicated Linux News 1 04-22-2013 04:12 AM
LXer: Tips and tricks: What is the 2038 bug? Is my system affected? How do I fix this LXer Syndicated Linux News 0 02-11-2008 10:40 PM
Year 2038 problem sudevank Linux - General 3 03-13-2007 11:09 PM
DHCP leases till 2038! abandoned. humbletech99 Linux - Networking 2 09-22-2006 03:50 AM
year 2038 problem masand Linux - News 11 04-08-2005 10:23 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 09:14 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration