I just ran a "zpool scrub" on my pool with version 2.3.1-1 and got:

scan: scrub repaired 0B in 00:16:17 with 0 errors on Tue May  6
17:06:50 2025

Before I do "zfs send | zfs recv", I'd like to ask what the reasoning
is that this should be able to fix it, if a scrub cannot?

Isn't there any "fsck" I can do right now that actually finds the issue
before I invest time (and also money for the external storage) in the
"zfs send | zfs recv" attempt and in the worst case find out that it
didn't help either?

Reply via email to