My ZFS seems to have swallowed something undisgestible, and is always trying to evict:
It tries to drive the ARC to the lowest allowed value, although there is ample free memory. And the ARC is already at its possible minimum with 19 MB:
If I move the
But when I put it back down, the target size will also go back down very fast, in a matter of seconds:
This has appeared tonight during some house-keeping jobs, it seems like some variable got an overflow, and now ZFS erroneously thinks it is utterly out of memory.
I didn't find a way to get rid of it (exept likely rebooting); it is certainly a bug, probably difficult to reproduce, and I will not bother to search for it.
I just post this here for the community to know that this can happen. If anybody else gets hit, You're welcome to pursue it further. Release is 11.3, on i386 (might well be an escaped 64bit conversion error with the value gone negative).
Code:
ARC Size: 49.92% 399.38 MiB
Target Size: (Adaptive) 25.00% 200.00 MiB
Min Size (Hard Limit): 25.00% 200.00 MiB
Max Size (High Water): 4:1 800.00 MiB
Code:
ARC: 411M Total, 42M MFU, 85M MRU, 2024K Anon, 235M Header, 46M Other
19M Compressed, 113M Uncompressed, 5.81:1 Ratio
If I move the
vfs.zfs.arc_min
up manually, the ARC does grow again:
Code:
ARC Size: 55.59% 444.76 MiB
Target Size: (Adaptive) 100.00% 800.00 MiB
Min Size (Hard Limit): 100.00% 800.00 MiB
Max Size (High Water): 1:1 800.00 MiB
But when I put it back down, the target size will also go back down very fast, in a matter of seconds:
Code:
ARC Size: 54.75% 438.03 MiB
Target Size: (Adaptive) 50.28% 402.25 MiB
Min Size (Hard Limit): 25.00% 200.00 MiB
Max Size (High Water): 4:1 800.00 MiB
ARC Size: 54.76% 438.06 MiB
Target Size: (Adaptive) 37.77% 302.13 MiB
Min Size (Hard Limit): 25.00% 200.00 MiB
Max Size (High Water): 4:1 800.00 MiB
This has appeared tonight during some house-keeping jobs, it seems like some variable got an overflow, and now ZFS erroneously thinks it is utterly out of memory.
I didn't find a way to get rid of it (exept likely rebooting); it is certainly a bug, probably difficult to reproduce, and I will not bother to search for it.
I just post this here for the community to know that this can happen. If anybody else gets hit, You're welcome to pursue it further. Release is 11.3, on i386 (might well be an escaped 64bit conversion error with the value gone negative).