From: Dave Chinner <david@fromorbit.com>
To: Hal Pomeranz <hal@deer-run.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: XFS 2038 rollover?
Date: Tue, 15 May 2018 14:58:42 +1000 [thread overview]
Message-ID: <20180515045842.GH23861@dastard> (raw)
In-Reply-To: <7BDFF86A-062B-4731-97E8-33E920CF7E7D@deer-run.com>
On Tue, May 15, 2018 at 12:33:01AM -0400, Hal Pomeranz wrote:
> I was curious about the roadmap for solving the 32-bit signed
> rollover issue for XFS (aka the “Y2K38” issue). You could
> cheat in a similar fashion to EXT4 and use the upper two bits of
> the nsec values to extend the seconds field to 34 bits. Or will
> the inode core be expanding to allow full 64-bit seconds values?
> Or is there some other plan?
>
> I’ve checked the FAQ and haven’t been able to find
> anything via Google.
Something along these lines:
https://lkml.org/lkml/2014/6/1/240
However, the VFS infrastructure I was asking for back in 2014 for
clamping timestamp ranges to the valid on-disk supported filesystem
range hasn't appeared yet, so there's a lot more work than just the
preliminary on-disk extended range support to be done....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2018-05-15 4:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 4:33 XFS 2038 rollover? Hal Pomeranz
2018-05-15 4:58 ` Dave Chinner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180515045842.GH23861@dastard \
--to=david@fromorbit.com \
--cc=hal@deer-run.com \
--cc=linux-xfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox