beegfs-fsck does not recognize missing chunks

[ttys42]

Describe the bug
When a file is split into multiple chunks and one or more of these chunks are missing, beegfs-fsck doesn't recognize this.

Describe the system
BeeGFS 8.3.1
Rocky 10.2
RoCE
Storage-Targets on ZFS

To Reproduce
Steps to reproduce the behavior:
$ dd if=/dev/random of=test.data bs=1M count=10
$ md5sum test.data
78d65093d0d9aa17d407e34eeebd051a test.data

$ beegfs entry info --retro --verbose test.data
...
EntryID: 1F7-6A3520BD-1
...

• 404 @ node_storage_4 [ID: 4]
• 501 @ node_storage_5 [ID: 5]
• 504 @ node_storage_5 [ID: 5]
• 604 @ node_storage_6 [ID: 6]
  Chunk path: u0/6A29/6/6F-6A296E8A-1/1F7-6A3520BD-1

-> ssh to node_storage_6 and rm /chunks/u0/6A29/6/6F-6A296E8A-1/1F7-6A3520BD-1

$ md5sum test.data
2a0a4155495d4adec72042c6f0e547a3 test.data

$ beegfs-fsck --checkfs --readonly
...

Expected behavior
Entry in /var/log/beegfs-fsck.log that chunk 604 for this file is missing

Log messages, error outputs
$ egrep "(test.data|6F-6A296E8A-1|1F7-6A3520BD-1)" /var/log/beegfs-fsck.out
-> no entry for this problem

Additional context
I also noticed many entries in other sections.
Unfortunately I could not find any documentation explaining what these errors mean exactly.

"Checking: Dentry-by-ID file is broken or missing"
-> What does this error mean?

"Chunk without an inode pointing to it (orphaned chunk)"
This is self-explanatory, but under what real-world conditions could this occur if the underlying filesystems (storage and meta) are intact?

"Checking: Attributes of file inode are wrong"
This shows many files but not what exactly is wrong with the attributes.