-
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
zdb -S ASSERT at ../../module/zfs/dsl_deadlist.c:308:dsl_deadlist_open()Aborted (core dumped) #15423
Comments
After upgrading to 2.2.0, [root@zfs9 ~]# cat /sys/module/zfs/version 2.2.0-1 I now get either [root@zfs9 ~]# time zdb -S scratch Simulated DDT histogram: bucket allocated referenced ______ ______________________________ ______________________________ refcnt blocks LSIZE PSIZE DSIZE blocks LSIZE PSIZE DSIZE ------ ------ ----- ----- ----- ------ ----- ----- ----- real 0m26.009s user 0m20.604s sys 0m28.306s [root@zfs9 ~]# time zdb -S scratch zdb: can't open 'scratch': Invalid exchange real 0m2.802s user 0m3.877s sys 0m3.901s [root@zfs9 ~]# time zdb -S scratch zdb: can't open 'scratch': Invalid exchange real 0m3.488s user 0m3.836s sys 0m4.214s |
Seeing the same assertion running This is on proxmox 8.2.5: Linux proxmox 6.8.12-1-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-1 (2024-08-05T16:17Z) x86_64 GNU/Linux ZFS version: zfs-2.2.6-pve1 It worked on a second run so the issue appeared transient. The cluster was not under heavy load at the time and a scrub had just been run a few days before with no errors. Pool is a mirror of 6 mirrors + a special vdev containing 2 mirrors. I was trying to see the block histogram to tweak the
|
FYI, the original system that I reported this problem on is now working while running RL8.10 and ZFS 2.2.5, [root@zfs9 ~]# uname -a Linux zfs9 4.18.0-553.16.1.el8_10.x86_64 #1 SMP Thu Aug 8 17:47:08 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux [root@zfs9 ~]# cat /sys/module/zfs/version 2.2.5-1 [root@zfs9 ~]# time zdb -S scratch Simulated DDT histogram: bucket allocated referenced ______ ______________________________ ______________________________ refcnt blocks LSIZE PSIZE DSIZE blocks LSIZE PSIZE DSIZE ------ ------ ----- ----- ----- ------ ----- ----- ----- 1 34.4M 3.67T 3.05T 3.14T 34.4M 3.67T 3.05T 3.14T 2 4.84M 566G 484G 495G 10.8M 1.24T 1.07T 1.09T 4 733K 89.9G 84.9G 85.5G 3.25M 408G 386G 389G 8 38.2K 4.57G 3.46G 3.59G 412K 49.3G 37.6G 39.1G 16 95.4K 9.34G 7.53G 7.95G 1.70M 175G 141G 149G 32 4.97K 476M 352M 376M 250K 23.5G 17.5G 18.7G 64 1.88K 146M 44.3M 61.4M 182K 13.6G 4.04G 5.68G 128 897 103M 47.6M 52.4M 160K 18.3G 8.29G 9.15G 256 658 76.1M 26.4M 30.4M 235K 27.2G 9.48G 10.9G 512 537 61.9M 19.9M 23.0M 376K 43.5G 14.0G 16.2G 1K 307 35.0M 11.6M 13.2M 426K 48.2G 16.0G 18.2G 2K 117 12.5M 4.15M 4.77M 311K 32.7G 11.0G 12.6G 4K 105 11.7M 850K 1.70M 447K 48.4G 4.10G 7.79G 8K 45 4.56M 4.44M 4.52M 416K 40.8G 39.6G 40.4G 16K 39 4.49M 4.32M 4.36M 1.12M 134G 129G 130G 32K 1 128K 18K 27.4K 32.7K 4.09G 589M 897M 256K 3 384K 292K 302K 827K 103G 78.4G 81.2G Total 40.0M 4.32T 3.62T 3.72T 55.2M 6.05T 5.00T 5.14T dedup = 1.38, compress = 1.21, copies = 1.03, dedup * compress / copies = 1.63 real 55m55.754s user 35m30.085s sys 23m50.757s so for my part this issue could be closed. |
System information
Describe the problem you're observing
zdb -S crashes with a core dump
Describe how to reproduce the problem
Note, after the debug information was gathered below a second attempt resulted in the same assertion failure,
Include any warning/errors/backtraces from the system logs
The text was updated successfully, but these errors were encountered: