Rich Ercolani

That's not a useful message, on its own; usually when something breaks like that, there will be another message that's not just "thread blocked for xyz seconds", and then because...

A number of companies like Klara will sell you support on contract. Without an explicit error message though, it's not really clear if that's needed for your case, because that...

Since you have refused to provide the information requested and insist that you are capable of deciding what's relevant in the logs, I am going to stop responding. Good luck.

If rewriting the spacemaps removes the assertion, that might suggest you still have lurking excitement eventually, since in theory that should be equally upset by duplicate range insertion, no? My...

Pathology in common with #14512 maybe?

(Replying here because I don't think commenting on that bug that this one seems unrelated is reasonable after I linked it here.) It might be unrelated, you'd have to see...

Hypothetically, it could be something like, you do something to access the VM image while it's idle (reading, not writing, just to be entirely clear), it dirties the file because...

> [9f69435](https://github.com/openzfs/zfs/commit/9f6943504aec36f897f814fb7ae5987425436b11) is the commit in 2.1.x that changed our behavior. It was first in 2.1.5. It goes back further and more wind-y than that, I think. First, there was...

This is absolutely still broken in 2.1.12 and 2.2.2, someone just ran into it today on IRC. (I see that it was marked closed because the original framing wasn't marked...

There's probably a bug to be found with this, but as a mitigation for either of you, do you have TLER configured on the failing drives? (e.g. smartctl -l scterc,RNUM,WNUM...