From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: xfs <linux-xfs@vger.kernel.org>
Subject: Re: [XFS SUMMIT] 64bit timestamps
Date: Thu, 23 Apr 2020 09:23:06 -0700 [thread overview]
Message-ID: <20200423162306.GL6742@magnolia> (raw)
In-Reply-To: <CAOQ4uxgeVZ8AYB-a7fXhKgh1GfCSfJL761a=Yot0jp4M56z_KA@mail.gmail.com>
On Thu, Apr 23, 2020 at 09:23:51AM +0300, Amir Goldstein wrote:
> On Thu, Apr 23, 2020 at 2:03 AM Darrick J. Wong <darrick.wong@oracle.com> wrote:
> >
> > Hi all,
> >
> > Here's a thread to talk about the remainder of 64-bit timestamp support
> > on XFS. I have a series[1] that redefines the inode timestamps to be
> > 64-bit nanosecond counters and decreases the accuracy of the ondisk
> > quota timers to 4s so that both will last until 2446.
> >
> > --D
> >
> > [1] https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git/log/?h=bigtime
>
> This looks great.
>
> What's the plan w.r.t. enabling bigtime on existing fs?
> In the end, it is just a administrative flag saying "point of no return".
> Everyone do realize that fixing y2038 by requiring to reformat
> existing filesystems is unacceptable for most of the deployments out there,
> right?
Ah, right, I neglected to post a link to the userspace counterpart:
https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfsprogs-dev.git/log/?h=bigtime
xfs_admin will be able to flip on the feature flag, after which the
kernel will start upgrading files to use the bigtime format.
--D
> Thanks,
> Amir.
prev parent reply other threads:[~2020-04-23 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 23:03 [XFS SUMMIT] 64bit timestamps Darrick J. Wong
2020-04-23 6:23 ` Amir Goldstein
2020-04-23 16:23 ` Darrick J. Wong [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=20200423162306.GL6742@magnolia \
--to=darrick.wong@oracle.com \
--cc=amir73il@gmail.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;
as well as URLs for NNTP newsgroup(s).