...
MWC checkers for other middleware on top of DAOS
the HDF5 DAOS VOL MWC checker is not implemented (only DFS and pydaos will be implemented for this work)
Some corruption cases for MW checkers:
A file that is corrupted (lost chunks in the array object) cannot be detected and the issue cannot be reported to the user.
An inode entry was partially corrupted (the akey value) which means some metadata on the corresponding object was lost (this could be mode_t, mtime, ctime, uid, gid, symlink value if entry was a symlink, etc.).
This is undetectable by the DFS MWC tool and won’t be discoverable until the user attempts to access that entry which it might not be able to or it has to ask for specific repair on the entry which can be provided as a later extension to the repair tool.
generic corruptions on the pool and container metadata (properties, attributes).
Outside of the Catastrophic recovery, a user might cause problems in the DFS namespace like creating a loop: dir1->dir2->dir3->dir1
Fixing such issues is out of scope for the the MWC checker tool for DFS.
...