https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-15281 Lustre <p>We have two clusters running, echo and lima.  Before I go further, we are comparing apples and oranges a bit here as:</p> <p>The MDT pool on echo is composed of two vdevs that are hardware RAIDs (legacy hardware) so no ZFS mirroring.  The MDT pool on lima is composed of 4 NVMe cards in 2 mirrors.</p> <p>The MDS on echo keeps getting very close to filling and we can't work out why.</p> <p>The two clusters are both used to do backups with heavy use of hard-linking (using dirvish/rsync).</p> <p>I know this is an oversimplification since it's not just inodes on the MDT but, running df -k and df -i to get kB and inodes used then dividing one by the other yields ~14kB/inode on echo and ~3kB/inode on lima.</p> <p>Are there any particular diagnostic tools/commands we could use to find what's using all the space on the ZFS MDT?</p> <p>echo's MDT is currently using 4.8TB for 350M inodes</p> <p>lima's MDT is currently using 2.8TB for 946M inodes</p> <p>Happy to provide any other info/params that might be useful.</p> CentOS 7.6 LU-15281

inode size disparity on ZFS MDTs

Bug Minor Open Unresolved Peter Jones Dneg Fri, 26 Nov 2021 22:31:03 +0000 Mon, 29 Nov 2021 21:01:48 +0000 0 3 <p>echo:  logicalused: 1.74TB, used: 4.73TB</p> <p>lima:  logicalused: 1.38TB, used: 2.74TB</p> <p>So lima is still way smaller per inode but the used/logicalused disparity is huge too.</p> <p>echo has physical block size of 4096, logical of 512</p> <p>lima has physical and logical of 512</p> <p>Both use 128K recordsize</p> <p>The first thing to check here would be whether <tt>ashift</tt> is different on the two pools. The lima filesystem may be using ashift=9 (512-byte sectors) and echo using ashift=12 (4096-byte sectors). ZFS will normally automatically select ashift based on the hardware sector size, even if the device claims a smaller sector size.</p> <p>Using ashift=9 on 4096-byte sector devices can dramatically hurt performance, as well as potentially cause data errors because of the internal read-modify-write of a sector may be modifying in-use blocks that are not part of the ZFS transaction causing errors in the "other" sub-sectors. This would <em>mostly</em> not be fatal, because of redundancy would likely allow those errors to be recovered, but they would be at risk if a device failed.</p> <p>zdb -U /etc/zfs/zpool.cache on both does show what you suggest in that lima's devices have an ashift of 9 and echo's are 12.</p> <p>Given the physical/logical block sizes reported by /sys/block this seems appropriate right?</p> <p>Without knowing deep internals of ZFS, it seems to me there are two things at play here (although I'll freely admit these are educated guesses):</p> <p>1) The logicalused/used disparity on echo - Is this explained by 4096/512/ashift-9?</p> <p>2) The logicalused/logicalused disparity between echo and lima - 1.7ish TB for 350M files on echo and 1.4ish TB for 946M on lima.</p> <p>The ashift value represents the smallest possible on-disk unit of allocation, so having a larger ashift is definitely going to inflate space usage. This can become significant with RAID-Z2, but is less so with mirrors.</p> <p>Since ZFS is always compressing metadata, and dnode allocation is done in larger chunks (64KB) the ratio of MDT space usage is 13.71KB/inode vs. 2.96KB/inode, 4.6x and not 8x as would be expected just from the ashift ratio. </p> <p>Unfortunately, this is a property of how ZFS is implemented.</p> <p>The only other possible cause for excessive space usage on the MDT would be if "echo" has an old Changelog user registered that is not consuming the records. This can be checked on the MDS with "<tt>lctl get_param mdd.&#42;.changelog_size</tt>". </p> <p>Output of that command:</p> <p>mdd.echo-MDT0000.changelog_size=0</p> <p>OK, that means there is no stray changelog usage, and it can't be the cause of the difference in space usage, so I think it is only the ashift. Unfortunately, the only way to change ashift is to reformat the whole pool, and even then that isn't recommended if the underlying storage is using 4KB sectors with 512-byte emulation, and will not work at all if it has only 4KB sector size. </p> <p>Ok thanks.</p> <p>Given the prevalence of 4k block devices now, I guess we're either gonna have to just grab more of those 512 NVMe cards, drastically increase our expected MDT size, or switch MDS back to ldiskfs.</p> Development Rank 1|i02az3: Rank (Obsolete) 9223372036854775807 Severity