Comment 79 for bug 1906476

Revision history for this message
Jonas Dedden (jonded94) wrote (last edit ):

I can also confirm that I am facing this bug, since I was running 5.13.0-19 for some short amount of time. I can not report any new broken files since I'm using 5.13.0-21-generic. I'm using an encrypted zfs filesystem.

Nevertheless, it seems like I still have a small handful of files that are broken in just one singular folder.

Even when I reboot into the Ubuntu recovery mode with additionally parameter zfs-recovery enabled, I receive Kernel panics when trying to ls the broken directory or remove the broken file:

VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl))
PANIC at zfs_znode.c:335:zfs_znode_sa_init()

After that even the recovery mode is not responding to any user inputs.

Is there any way to remove the broken directory?