On Mon, Apr 4, 2022, at 3:51 PM, Justin Forbes wrote: > On Mon, Apr 4, 2022 at 11:47 AM Colin Walters <walt...@verbum.org> wrote: >> >> Hi, creating a thread on this from: >> https://github.com/coreos/fedora-coreos-config/pull/1650 >> >> Basically I'd propose that not just our default images have y2038-compatible >> filesystem setups, we ensure that if e.g. XFS is explicitly chosen for a >> Workstation installation then it is set up with bigtime=1. >> >> (Note btrfs uses 64 bit time today, so I think this is mostly about ext4 and >> xfs, but perhaps we also need to look at the longer tail too, e.g. squashfs. >> OTOH, because squashfs is read-only we can just worry about that closer to >> 10 years from now...) >> >> If no one objects I guess I can look at re-learning Mediawiki syntax again >> and writing a Change. > > Or, you could ignore it and it will happen anyway: > > xfsprogs-5.15.0-rc1 (11 Mar 2022) > - mkfs: enable inobtcount and bigtime by default (Darrick J. Wong)
Ah, thanks for the link. So...given the ext4 34 bit thing, I think as long as we ship that by default in say F37 we can just mostly call this done. (I'd still like to enable 256 bit inodes for ext4 /boot type setups just for completeness though) _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
