@elladan
@mcc Copy-on-write filesystems like ZFS and Btrfs don’t need fsck-like tools, because it is inherently impossible for the filesystem to get into an inconsistent state under normal operation short of a bug in the filesystem. At that point, the fsck would also be untrustworthy.
Fully-journaled filesystems should also be impossible to corrupt when used in fully-journaled mode. fsck *should* only matter for filesystems which are unjournaled or partially-journaled (or used in such a mode).