The chunk tree lives in system chunks, which carry no METADATA bit, so the
whole-stripe rule that stripe_meta applies to raid56 tree blocks never
applied to it: chunk tree blocks were placed by the clustered allocator,
sharing stripes with chunk tree blocks committed earlier, and every chunk
tree COW was a read-modify-write of such a stripe. The RMW audit measured
it (meta_rmw_old over system chunks during chunk churn), and the mount
warned about it. A torn parity rewrite there is the worst write hole the
filesystem can take: with a member then lost, the committed chunk tree
block that shared the stripe reconstructs wrong, the checksum rejects it,
and nothing maps -- the degraded mount fails, and there is no second copy.
Include system block groups in btrfs_is_stripe_meta_bg(). Everything
downstream already keys on that predicate: the whole-stripe allocation in
do_allocation_stripe(), the trapped-space accounting, the covered/uncovered
decision in the RMW report and the audit. The four walks that select
groups by space_info flags (the enable-time sweep, the unusable-space scan,
the reclaim tick, the commit-time metadata run retirement) gain SYSTEM
alongside DATA and METADATA, so system groups are armed, scanned, reclaimed
when trapped, and have their runs closed after the commit's tree writes
like metadata groups.
reserve_chunk_space() sizes its request in tree blocks, but a chunk tree
COW that needs a fresh run takes a whole stripe for its first block; the
trapped bytes and the open run's remainder are already counted as used, so
what is left is whole free stripes, and the check now demands one stripe
of headroom beyond the request -- deciding when to allocate the next
system chunk, without reserving the headroom -- or the chunk item for that
very allocation could find no stripe to land in.
The "does not cover raid56 system chunks" warning has nothing left to
warn about and goes.