Brian Behlendorf

@Avamander the crashes you observed occurred in unrelated areas of the code and both suggest kernel memory corruption. Is there anything else you changed on the system which might explain...

@gamanakis I think this change would be reasonable to cherry pick in to the stable release. I've opened #13768 against the 2.1.6 staging branch.

You might try the recent and 2.1.0 tag, I know some improvements were made in this area but I'm not sure if this specific issue was resolved.

That is surprising, the space usage should be close to what's reported for a similar raidz config. Using the 2.1.5 release I wasn't able to reproduce this. Can you double...

@gleb-shchavlev I looked in to this a bit and the decrease in reported usable capacity is caused by: 1) relatively wide RAID stripe width 16d+2p, and 2) the 4k sector...

> Is it correct to create a draid with so many (32d) disks? Generally I'd recommend against going larger than about 16 data disks. As you can see from your...

If this PR is ready for review would you mind rebasing it on current master branch, squashing the commits, and force updating the PR.

I can absolutely understand why the new sequential scrub and resilver behavior may be confusing. The code is working as intended. However, unlike the legacy scrub the sequential scrub design...

That's exactly right. I believe part of the confusion here is that we don't currently provide any administrative interface to report on when the last scrub checkpoint was taken. Nor...

No update, but I've gone ahead and marked this as "Not Stale" to make sure it stays open.