8 Reporting an Issue
Luchesar ILIEV edited this page 2026-07-12 17:38:31 +03:00

Reporting an Issue

Use the archzfs/archzfs issue tracker for reproducible problems with current ArchZFS packages, package generation, or the GitHub-hosted Pacman repository.

Before opening an issue:

  1. Update repository metadata and confirm that the problem still occurs with the current GitHub release rather than the legacy archzfs.com repository.
  2. Search existing open and recently closed issues and pull requests.
  3. Determine whether the problem belongs to ArchZFS, Arch Linux packaging, the Linux kernel, or upstream OpenZFS.
  4. Do not report a kernel-specific package as out of date until the matching official Arch kernel version is available from the repository source used by the ArchZFS build.

Include:

  • Exact ArchZFS, OpenZFS, kernel, and package versions.
  • Whether the prebuilt kernel package or zfs-dkms is installed.
  • The configured ArchZFS server URL and signature policy.
  • Steps to reproduce the problem and complete relevant command output.
  • Links to related Arch Linux or OpenZFS reports when the root cause may be upstream.
  • Recent package-manager, DKMS, initcpio, module-loading, or workflow logs as appropriate, with secrets and unrelated personal information removed.

Use ArchZFS Discussions for broad support questions, design proposals, or topics that are not yet actionable bug reports.

Maintainers may request more information or close reports that cannot be reproduced. Maintainers apply both standard GitHub labels and the current letter-prefixed taxonomy: C-* for category, E-* for experience or effort, P-* for priority, and S-* for status. Consult the repository's current label list because available values may change.