NetApp
Configurable volume to accommodate LUN metadata
Describe the solution you'd like Currently, Trident defaults to allocating 10% of PV volume to LUN metadata. Some users deploy Trident PVs with sizes greater than 100GB In this case, it seems that allocating 10% of the volume for LUN metadata is unnecessary. At the same time, our team would like to allocate 20% of the LUN for metadata, as we often work with smaller PVs and want to ensure data protection. To address all these issues at once, we suggest allowing users to configure the amount of space allocated for LUN metadata within their volumes.
Just to better understand the use case: What drives your requirement to have 20% for LUN metadata? From my experience it should never be that much?
Just to better understand the use case: What drives your requirement to have 20% for LUN metadata? From my experience it should never be that much?
We want to allocate 20% of the available space on the LUN for metadata because we have experienced situations where the discard mount option was not enabled at the operating system level. When working with small disk sizes (up to 100 GB), the LUN was approximately 99% full, and when a large load was applied to the disk, the LUN would overflow, causing the volume to overflow and input to stop. Allocating 20% for LUN metadata would protect us from these scenarios.
I have a similar problem where it seems that LUN metadata of 10% is not enough to handle a filesystem being filled (https://github.com/NetApp/trident/issues/903). Having the filesystem being full should not trigger error on the storage array side.
