-
Could someone either point me at a good explanation about how volume actual size and size limit work when snapshots exist? To elaborate, I noticed that the snapshot size is counted towards actual size. When I delete a snapshot, the actual size goes down. Sometimes, I see a volume actual size can be larger than the volume size limit. Ive seen applications write data to that volume without a problem with the actual size growing well beyond the size limit. while another time I had an application crash because the size limit was reached. This makes it confusing for me to determine when a volume is actually really about to grow beyond its real hard size limit (ie, app going to crash or denied write action), or to determine how much is actually really still free, even though the actual size is showing larger than the volume size limit. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
Did you mean https://longhorn.io/docs/1.7.2/references/settings/#snapshot-maximum-count? |
Beta Was this translation helpful? Give feedback.
Currently, Longhorn actual size is the sum the sizes of volume head (active data) and snapshots. We can improve this.
https://longhorn.io/docs/1.7.2/nodes-and-volumes/volumes/volume-size
For now, you can get the statistics by https://longhorn.io/docs/1.7.2/monitoring/kubelet-volume-metrics/.