Critical ZFS crash: VERIFY3(0 == dmu_object_claim_dnsize(zfsvfs->z_os... failed (0 == 28)

Don Daniello

Active Member
Jan 28, 2012
We just experienced a nasty crash whenever kernel touched our ZFS pool. This occured after we replaced one faulty drive and resilvered but in fact had nothing to do with that.

The crash bug occurs when ZFS is trying to reapply ZIL due to a previous power loss. The issues linked below document the detailed problem, symptoms and potential solutions. They helped us recover from that issue.

Partial trace (like this:
 kernel:[  149.314630] VERIFY3(0 == dmu_object_claim_dnsize(zfsvfs->z_os, obj, DMU_OT_PLAIN_FILE_CONTENTS, 0, obj_type, bonuslen, dnodesize, tx)) failed (0 == 28)

Related PRs/issues:
* tuxoko/zfs commit fixing the issue: (refers to 3 issues against zfsonlinux/zfs listed below)
* Issue 1:
* Issue 2:
* Issue 3:
* Merged PR in zfsonlinux/zfs:
* Helpful workarounds: and

Since the bug has been fixed in zfsonlinux/zfs, it is up to the Proxmox team to release a kernel version with the patch - probably backported, since zfsonlinux releases are rare.
Thanks for the report!
We try to follow ZFS point releases (and the first patchset for 0.8.2 recently hit the ZFS lists) - once they are out we try to include them (after some testing).

You could ask upstream ( to include this commit for 0.8.2 (it would make all other ZFS users profit from the fix as well)


The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!