-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PANIC: blkptr has invalid CHECKSUM 0 #12349
Comments
Immediate question: maybe 958826b makes your life better? I don't think it's a listed failure mode, but I'd give it a shot. Other thought: are any of the datasets you're receiving encrypted? Because there are a couple of outstanding issues with invalid data winding up in the pipeline with encrypted send/recv... (Amused aside: hey, I used to own that exact motherboard.) |
I'll give current master a spin to see if 958826b helps and report back when/if it panics again. Of the sent datasets a single one is encrypted (sent raw), but IIRC the panics/hangs happenned on the other datasets. |
That was quick:
|
I've recreated the pool, so there's nothing to be done here anymore except wonder what the original problem cause was... |
I have seen a few stale issues with similar title, however my stack traces look somewhat different, so I'm opening a new issue. I'm trying to figure out if I have a hardware problem or if my pool is actually borked, possibly caused by a bug.
System information
Describe the problem you're observing
The system functions purely as a backup receiving sends and deleting old snapshots. After 1-10 days of running, the system panics while receiving with strack trace variations of "blkptr has invalid CHECKSUM 0". The pool then hangs indefinitely, requiring a reboot. Subsequent scrubs comes back clean.
Describe how to reproduce the problem
I can reproduce by leaving the system receiving backups for a few days. I don't know how to reproduce on another system.
Include any warning/errors/backtraces from the system logs
The text was updated successfully, but these errors were encountered: