"For anyone who hit this issue you should be able to fix the panic by temporarily enabling the zfs_recover module option (set /sys/module/zfs/parameters/zfs_recover=1). This will convert the panic in to a warning for any effected files/directories/symlinks/etc. Since the mode information is what was long the code will assume the inode is a regular file and you should be able to remove it."
Just for clarification, fixing the corruption caused by panic as noted in https:/ /github. com/openzfs/ zfs/issues/ 11474 is as follows:
"For anyone who hit this issue you should be able to fix the panic by temporarily enabling the zfs_recover module option (set /sys/module/ zfs/parameters/ zfs_recover= 1). This will convert the panic in to a warning for any effected files/directori es/symlinks/ etc. Since the mode information is what was long the code will assume the inode is a regular file and you should be able to remove it."