Reproducible XFS Filesystems Builds for VMs

[Luca DiMaio]

Dear list

As of this week xfsprogs 6.17.0 has been released and included is the
patch that I managed to submit:
https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/commit/?id=8a4ea72724930cfe262ccda03028264e1a81b145

It is now possible to populate an XFS filesystem, similarly to how ext4 works

I'd like to contribute to the docs of
https://reproducible-builds.org/docs/system-images/ to add an XFS
section
could someone point me to the repo/mailing list for that?

Thanks a lot
L.

On Mon, Apr 28, 2025 at 11:25 AM Luca DiMaio <luca.dimaio at chainguard.dev> wrote:
>
> At the moment we're at v7 of the patch set which adds ability to
> populate from a directory, much like ext4:
> https://lore.kernel.org/linux-xfs/20250426135535.1904972-1-luca.dimaio1@gmail.com/T/#t
>
> By default atime/ctime/crtime is set to `gettimeofday()` while mtime
> is preserved
> that can be easily worked around with something like `libfaketime` or
> similar libraries to enforce a date
>
> L.
>
> On Thu, Apr 24, 2025 at 3:46 PM Bernhard M. Wiedemann
> <bernhardout at lsmod.de> wrote:
> >
> > On 16/04/2025 16.55, Luca DiMaio via rb-general wrote:
> > > At the moment I've opened an RFC in the XFS mailing list, to improve their
> > > prototype file functionality, in particular to carry over the inode's timestamps
> > > from source:
> >
> > If these include ctime and atime, those are usually hard to reproduce in
> > a filesystem.
> > It would probably be good to have an option to clamp timestamps to a
> > maximum, similar to tar's --clamp-mtime option or set them all to a
> > given constant value.