lundman
commented
4 years ago There currently is something going on that is suspect. You can create a new pool, and sometimes, it will have data errors on it. If you issue scrub and clear, twice, they will go away.
Since this is not a problem on other platforms, it is something that happens in the Windows port - possibly uninitialised memory, incorrect error code handling after IO etc.
But I am not sure it is directly related to the lz4 problem, since in your experience the corruption goes away if you disable lz4.
Reported by datacore.
we have a homemade tool that pumps I/Os to disks and verifies the accuracy of the data written to spot data miscompares (we use it all the time to validate our software) and the tool spits out lots of miscompares when I started it on that ZVOL. I tried on another pool without the compression=lz4 and the miscompares are gone. Just FYI but compression could also be the culprit for the slab free issue. Running for a little time gives me another BSOD with compression off, different from the one I report now so I'll keep it for later and will take a stab at it first.