Reviewed by: George Wilson <[email protected]> Reviewed by: Prakash Surya <[email protected]>
If snapshots are being periodically created, scrub/resilver may never complete (or may take a long time to complete). The symptom is that the scrub gets "stuck" at 99+% done (according to "zpool status"). ::zfs_dbgmsg reveals that we are traversing a snapshot that was created long after the scrub started. In particular, the scn_cur_min_txg is >= scn_cur_max_txg. This snapshot can't reference any blocks that need to be scrubbed, so we are just wasting time reading its metadata looking for blocks to scrub. You can view, comment on, or merge this pull request online at: https://github.com/openzfs/openzfs/pull/55 -- Commit Summary -- * 6450 scrub/resilver unnecessarily traverses snapshots created after the scrub started -- File Changes -- M usr/src/uts/common/fs/zfs/dsl_scan.c (54) -- Patch Links -- https://github.com/openzfs/openzfs/pull/55.patch https://github.com/openzfs/openzfs/pull/55.diff --- Reply to this email directly or view it on GitHub: https://github.com/openzfs/openzfs/pull/55
_______________________________________________ developer mailing list [email protected] http://lists.open-zfs.org/mailman/listinfo/developer
