No. ZFS has features that provide the same end results as "fsck", but without a separate fsck binary.
For example, you can run zpool scrub <poolname> to run a background process that will double-check the data in the pool, using the checksums that are stored in the pool. If there are any mis-matched checksums, the data is recreated from redundant data stored in the pool. This is similar in function to a "background fsck" except that is can actual repair bad data.
In newer versions of ZFS, if there's an issue that prevents the pool from being imported, you are given the option to roll-back one transaction group, which gets you back to a known-good status. (Previously, one had to do this manually using zdb and other arcane "magic" commands. This is not yet in FreeBSD's port of ZFS.)
Thus, you get a working pool, with known-good data, without ever having a separate "fsck" binary. Which is better, since fsck just checks the filesystem metadata, and never checks/fixes the actual file data. Something that ZFS does!!
|