You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am experiencing a recurring issue with disk storage management in UTMStack. Even though I have configured a log retention policy of 180 days and the "cold storage" flag is disabled, my disk usage continues to grow until it triggers the 70% threshold alert, and eventually nears the 85% mark.
Environment details:
UTMStack Version: v10.9.5-202606021041
Storage Setup: /utmstack is mounted on a dedicated, separate hard drive.
Retention Policy: 180 days.
Cold Storage: Disabled.
The issue:
Whenever I receive the 70% capacity warning, I increase the disk size. However, after a few weeks, the storage usage climbs back up to the 70% threshold, prompting the same alerts again. I am essentially forced to continuously increase the disk size, which suggests that the automatic cleanup process might not be behaving as expected, or that I am misunderstanding the retention mechanics.
My questions:
Retention Logic: Does the system wait until the 85% "auto-delete" threshold is reached to effectively purge logs older than 180 days, rather than consistently pruning them based on the 180-day policy?
Diagnostics: Is there a way to investigate which sensors or timeframes are consuming the most storage? Could you provide guidance on:
API calls or SQL queries (if applicable) to analyze data volume by source/date?
Specific paths or files within /utmstack/ that I should inspect to identify the "heavy" data contributors?
I would appreciate any advice on how to troubleshoot this behavior and ensure that the retention policy is being enforced correctly.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I am experiencing a recurring issue with disk storage management in UTMStack. Even though I have configured a log retention policy of 180 days and the "cold storage" flag is disabled, my disk usage continues to grow until it triggers the 70% threshold alert, and eventually nears the 85% mark.
Environment details:
UTMStack Version: v10.9.5-202606021041
Storage Setup: /utmstack is mounted on a dedicated, separate hard drive.
Retention Policy: 180 days.
Cold Storage: Disabled.
The issue:
Whenever I receive the 70% capacity warning, I increase the disk size. However, after a few weeks, the storage usage climbs back up to the 70% threshold, prompting the same alerts again. I am essentially forced to continuously increase the disk size, which suggests that the automatic cleanup process might not be behaving as expected, or that I am misunderstanding the retention mechanics.
My questions:
Retention Logic: Does the system wait until the 85% "auto-delete" threshold is reached to effectively purge logs older than 180 days, rather than consistently pruning them based on the 180-day policy?
Diagnostics: Is there a way to investigate which sensors or timeframes are consuming the most storage? Could you provide guidance on:
API calls or SQL queries (if applicable) to analyze data volume by source/date?
Specific paths or files within /utmstack/ that I should inspect to identify the "heavy" data contributors?
I would appreciate any advice on how to troubleshoot this behavior and ensure that the retention policy is being enforced correctly.
Thank you for your support!
Beta Was this translation helpful? Give feedback.
All reactions