andersenep
Cadet
- Joined
- Dec 7, 2020
- Messages
- 4
I have a drive that encountered 15 read errors during a scheduled scrub. Upon sourcing a replacement drive (several weeks later), I checked zpool status to identify which disk it was, and the errors had somehow been cleared.
Not sure what happened, ran another scrub and got 1 CKSUM error. It was da11.
Reboot and check zpool status:
It seems like checking/nagging me to update to openzfs 2.0 is essentially running zpool clear on my pools. As a user, I am far more concerned with my scrub results being properly handled than I am with openzfs 2.0 awareness.
Code:
pool: storage state: ONLINE status: Some supported features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that does not support the features. See zpool-features(5) for details. scan: scrub repaired 896K in 06:16:00 with 0 errors on Sun Nov 22 06:16:01 2020 config: NAME STATE READ WRITE CKSUM storage ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 da6 ONLINE 0 0 0 da3 ONLINE 0 0 0 da9 ONLINE 0 0 0 raidz1-1 ONLINE 0 0 0 da5 ONLINE 0 0 0 gptid/cbe9e8e5-0d8f-11eb-a1ae-00e081e51614 ONLINE 0 0 0 /* the first & last time i let webui replace a drive */ da8 ONLINE 0 0 0 raidz1-2 ONLINE 0 0 0 da4 ONLINE 0 0 0 da1 ONLINE 0 0 0 da11 ONLINE 0 0 0 raidz1-3 ONLINE 0 0 0 da2 ONLINE 0 0 0 da0 ONLINE 0 0 0 da10 ONLINE 0 0 0 cache da12 ONLINE 0 0 0 errors: No known data errors
Not sure what happened, ran another scrub and got 1 CKSUM error. It was da11.
Code:
pool: storage state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-9P scan: scrub repaired 64K in 06:20:56 with 0 errors on Mon Dec 7 02:41:21 2020 config: NAME STATE READ WRITE CKSUM ------ da11 ONLINE 0 0 1 ------
Reboot and check zpool status:
Code:
pool: storage state: ONLINE status: Some supported features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that does not support the features. See zpool-features(5) for details. scan: scrub repaired 64K in 06:20:56 with 0 errors on Mon Dec 7 02:41:21 2020 config: NAME STATE READ WRITE CKSUM ------ da11 ONLINE 0 0 0 ------
It seems like checking/nagging me to update to openzfs 2.0 is essentially running zpool clear on my pools. As a user, I am far more concerned with my scrub results being properly handled than I am with openzfs 2.0 awareness.