-
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
Exabyte dedup_table_size reported on ZFS 2.3 without fast dedup. #17019
Comments
I think the issues goes away after I do some writes using the same hash algorithm, but I'm not 100% sure if that what triggered the correct numbers to appear. It definitely stayed broken before that when I was writting new data using different dedup hash function. |
I am experiencing the same issue on my test environments, here are the details. Let me know if you need more I ran the upgrade twice and both times I encountered this issue. Pre-upgrade
zpool status -D vpool1
pool: vpool1
state: ONLINE
config:
NAME STATE READ WRITE CKSUM
vpool1 ONLINE 0 0 0
scsi-36000c29dcd74a9ea30c6559724c2e5b1 ONLINE 0 0 0
errors: No known data errors
dedup: DDT entries 249386, size 267B on disk, 145B in core
bucket allocated referenced
______ ______________________________ ______________________________
refcnt blocks LSIZE PSIZE DSIZE blocks LSIZE PSIZE DSIZE
------ ------ ----- ----- ----- ------ ----- ----- -----
1 224K 28.1G 28.1G 28.1G 224K 28.1G 28.1G 28.1G
32 18.9K 2.37G 2.37G 2.37G 954K 119G 119G 119G
512 200 25M 25M 25M 106K 13.2G 13.2G 13.2G
Total 244K 30.4G 30.4G 30.4G 1.25M 161G 161G 161G zdb -D vpool1
DDT-sha256-zap-duplicate: 19575 entries, size 244 on disk, 132 in core
DDT-sha256-zap-unique: 229811 entries, size 269 on disk, 146 in core
dedup = 5.27, compress = 1.00, copies = 1.00, dedup * compress / copies = 5.27 Post-upgrade, in my case there was also a kernel bump.
zpool status -D vpool1
pool: vpool1
state: ONLINE
config:
NAME STATE READ WRITE CKSUM
vpool1 ONLINE 0 0 0
scsi-36000c29dcd74a9ea30c6559724c2e5b1 ONLINE 0 0 0
errors: No known data errors
dedup: DDT entries 249386, size 16.0E on disk, 34.5M in core
bucket allocated referenced
______ ______________________________ ______________________________
refcnt blocks LSIZE PSIZE DSIZE blocks LSIZE PSIZE DSIZE
------ ------ ----- ----- ----- ------ ----- ----- -----
1 224K 28.1G 28.1G 28.1G 224K 28.1G 28.1G 28.1G
32 18.9K 2.37G 2.37G 2.37G 954K 119G 119G 119G
512 200 25M 25M 25M 106K 13.2G 13.2G 13.2G
Total 244K 30.4G 30.4G 30.4G 1.25M 161G 161G 161G zdb -D vpool1
DDT-sha256: version=0 [LEGACY]; flags=0x00; rootobj=1
DDT-sha256-zap-duplicate: dspace=4780032; mspace=2588672; entries=19575
DDT-sha256-zap-unique: dspace=61882368; mspace=33587200; entries=229811
dedup = 5.27, compress = 1.00, copies = 1.00, dedup * compress / copies = 5.27 |
System information
Describe the problem you're observing
I tried to make sense of new pool properties before migrating to fast dedup. The output puzzled me:
Describe how to reproduce the problem
I didn't do anything special, I have updated to ZFS-2.3.0 from ZFS-2.2.7 and didn't do any feature upgrades (carefully considering migrating to fast dedup). I'm pretty sure ZFS 2.2.7 had reasonable value for size on disk.
Looks like reporting is off for legacy dedup, which makes it kinda scary to upgrade the pool and try the new feature.
For comparison the output from
zpool status -D net
on ZFS 2.2.7.The text was updated successfully, but these errors were encountered: