linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Donald Buczek <buczek@molgen.mpg.de>
To: linux-xfs@vger.kernel.org
Subject: [QUESTION] zig build systems fails on XFS V4 volumes
Date: Sat, 3 Feb 2024 18:50:31 +0100	[thread overview]
Message-ID: <1b0bde1a-4bde-493c-9772-ad821b5c20db@molgen.mpg.de> (raw)

Dear Experts,

I'm encountering consistent build failures with the Zig language from source on certain systems, and I'm seeking insights into the issue.

Issue Summary:

     Build fails on XFS volumes with V4 format (crc=0).
     Build succeeds on XFS volumes with V5 format (crc=1), regardless of bigtime value.

Observations:

     The failure occurs silently during Zig's native build process.
     The build system relies on timestamps for dependencies and employs parallelism.
     Debugging is challenging without debug support at this stage, and strace output hasn't been illuminating.

Speculation:

     The issue may be related to timestamp handling, although I'm not aware of significant differences between V4 and V5 formats in this regard.

Questions:

     Why might a dependency build system behave differently on XFS V4 vs. V5 volumes? Could this be a race condition, despite consistent failure on V4 and success on V5 in repeated tests?

Any guidance or suggestions would be greatly appreciated.

Thank you for your time and expertise.

Please let me know if you need any further information or clarification.

Best regards,

   Donald

-- 
Donald Buczek
buczek@molgen.mpg.de
Tel: +49 30 8413 1433

             reply	other threads:[~2024-02-03 17:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-03 17:50 Donald Buczek [this message]
2024-02-04 21:56 ` [QUESTION] zig build systems fails on XFS V4 volumes Dave Chinner
2024-02-05 13:12   ` Donald Buczek
2024-02-05 21:13     ` Dave Chinner
2024-02-06  6:45       ` Donald Buczek

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=1b0bde1a-4bde-493c-9772-ad821b5c20db@molgen.mpg.de \
    --to=buczek@molgen.mpg.de \
    --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).