ztest should update the cachefile before killing itself
zfs - Zettabyte File System
From George Wilson:
While running zloop I've seen many cases where ztest fails because zdb was unable to open the pool. The ztest program will invoke zdb using the -U option to specify the pool cache file. Unfortunately the cache file may be out of data since it's updated asynchronously. The typical scenario is where the zpool.cache file believes that the pool contains either a 'mirror' or 'replacing' vdev but the MOS config no longer shows the logical vddv in the configuration. This means either the replace operation finished or one of the leaf vdevs was detached from the mirror.
Updated by Christopher Siden almost 10 years ago
- Status changed from In Progress to Closed
commit b4952e1 Author: George Wilson <firstname.lastname@example.org> Date: Wed Aug 7 13:16:22 2013 3956 ::vdev -r should work with pipelines 3957 ztest should update the cachefile before killing itself 3958 multiple scans can lead to partial resilvering 3959 ddt entries are not always resilvered 3960 dsl_scan can skip over dedup-ed blocks if physical birth != logical birth 3961 freed gang blocks are not resilvered and can cause pool to suspend 3962 ztest should print out zfs debug buffer before exiting Reviewed by: Matthew Ahrens <email@example.com> Reviewed by: Adam Leventhal <firstname.lastname@example.org> Approved by: Richard Lowe <email@example.com>