Bug 242319 - dmu_object_claim_dnsize in zfs_znode.c results in a kernel panic upon FS mount
Summary: dmu_object_claim_dnsize in zfs_znode.c results in a kernel panic upon FS mount
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 12.0-STABLE
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-fs mailing list
URL:
Keywords: panic
Depends on:
Blocks:
 
Reported: 2019-11-30 09:44 UTC by Zane C. Bowers-Hadley
Modified: 2019-12-01 11:04 UTC (History)
1 user (show)

See Also:


Attachments
screenshot of the kernel panic (728.51 KB, image/jpeg)
2019-11-30 09:44 UTC, Zane C. Bowers-Hadley
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Zane C. Bowers-Hadley 2019-11-30 09:44:04 UTC
Created attachment 209547 [details]
screenshot of the kernel panic

I've attached a screenshot of the kernel panic.

Currently consistently reproducible via mounting the FS in question.

uname -a
FreeBSD vixen42.vulpes.vvelox.net 12.1-STABLE FreeBSD 12.1-STABLE r354803 vixen42  amd64

Only change from the default is the inclusion of ALTQ.


On a similar note, came across this. Not sure how relevant it... https://github.com/zfsonlinux/zfs/issues/8910


Post a long SMART self test finishing, going to try setting vfs.zfs.zil_replay_disable to 1 and seeing if I can mount it that way.
Comment 1 Andriy Gapon freebsd_committer 2019-11-30 16:08:08 UTC
Just a note that in my opinion the ZoL issue is the same problem.
Comment 2 Zane C. Bowers-Hadley 2019-11-30 20:03:26 UTC
(In reply to Andriy Gapon from comment #1)

Yup. Definitely looks to be the same issue. Post SMART self test finishing, I set sysctl vfs.zfs.zil_replay_disable=1 and it mounted with out issue then.