From bc9b699b9ab134f7b03fcd37ab5a66a8b4d70ee6 Mon Sep 17 00:00:00 2001 From: hco-bot <71450783+hco-bot@users.noreply.github.com> Date: Wed, 4 Feb 2026 04:57:14 +0000 Subject: [PATCH] Sync CNV runbook GuestFilesystemAlmostOutOfSpace.md (Updated at 2026-02-03 12:16:09 +0000 UTC) --- .../GuestFilesystemAlmostOutOfSpace.md | 26 +++++++++---------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/alerts/openshift-virtualization-operator/GuestFilesystemAlmostOutOfSpace.md b/alerts/openshift-virtualization-operator/GuestFilesystemAlmostOutOfSpace.md index 4a765f6a..9ac3743f 100644 --- a/alerts/openshift-virtualization-operator/GuestFilesystemAlmostOutOfSpace.md +++ b/alerts/openshift-virtualization-operator/GuestFilesystemAlmostOutOfSpace.md @@ -7,9 +7,9 @@ of available disk space. The alert has the following severity levels: -- **Warning**: Triggers when file-system usage is between 85% and 95% for 5 +- **Warning**: Triggers when file system usage is between 85% and 95% for 5 minutes. -- **Critical**: Triggers when file-system usage exceeds 95%. +- **Critical**: Triggers when file system usage exceeds 95%. The alert provides details about the specific file system (`disk_name`), its mount point (`mount_point`), the VMI name, and namespace. @@ -29,7 +29,7 @@ application or system failure. ## Diagnosis -1. Check the file-system usage metrics for the VMI: +- Check the file-system usage metrics for the VMI: ```bash # Get the domain name of the VMI @@ -41,7 +41,7 @@ application or system failure. $ oc exec -it -n -- virsh qemu-agent-command '{"execute": "guest-get-fsinfo"}' ``` -2. You can also connect to the VMI by using the `virtctl` console to inspect +- You can also connect to the VMI by using the `virtctl` console to inspect disk usage in the guest OS: ```bash @@ -87,24 +87,24 @@ disk usage in the guest OS: $ virtctl restart -n ``` - This step causes the disk.img to be resized to match the new PVC size. - While this is primarily needed for filesystem volumes, it's recommended - to always restart for consistency. + This step resizes the disk.img to match the new PVC size. + While this is primarily needed for file system volumes, restarting to +apply changes in generally recommended. ### Long-term Solutions -1. **Set up log rotation and cleanup policies** within guest operating systems. +- **Set up log rotation and cleanup policies** within guest operating systems. -2. **Use appropriate volume sizes** when provisioning VMs based on expected +- **Use appropriate volume sizes** when provisioning VMs based on expected workload requirements. -3. **Consider using dynamic storage provisioning** with StorageClasses that +- **Consider using dynamic storage provisioning** with StorageClasses that support volume expansion. -4. **Implement automated cleanup scripts** or maintenance tasks within VMs to +- **Implement automated cleanup scripts** or maintenance tasks within VMs to manage disk space proactively. -5. **Review and optimize application storage patterns** to minimize unnecessary +- **Review and optimize application storage patterns** to minimize unnecessary disk usage. If the issue persists or the file system continues to fill up rapidly after @@ -112,5 +112,5 @@ cleanup, investigate the root cause such as application bugs, excessive logging, or unexpected data growth. If you cannot resolve the issue, log in to the -[Customer Portal](https://access.redhat.com) and open a support case, +[Red Hat Customer Portal](https://access.redhat.com) and open a support case, attaching the artifacts gathered during the diagnosis procedure. \ No newline at end of file