From 3f53e4c8d03bb59acacd32c3c7d56ec7029b6751 Mon Sep 17 00:00:00 2001 From: Vicente Cheng Date: Sat, 1 Jun 2024 00:34:50 +0800 Subject: [PATCH] KB: Clarify the impacted version of filesystem trim Signed-off-by: Vicente Cheng --- .../the_potential_risk_with_fstrim.md | 18 ++++++++++++++++-- 1 file changed, 16 insertions(+), 2 deletions(-) diff --git a/kb/2024-01-30/the_potential_risk_with_fstrim.md b/kb/2024-01-30/the_potential_risk_with_fstrim.md index e1616f5c..cd0644ab 100644 --- a/kb/2024-01-30/the_potential_risk_with_fstrim.md +++ b/kb/2024-01-30/the_potential_risk_with_fstrim.md @@ -12,10 +12,24 @@ hide_table_of_contents: false --- :::note -This issue is already resolved by Longhorn v1.5.4, v1.6.1, v1.7.0 and later versions. -::: +Filesystem trim is introduced in Longhorn v1.4.0. + +Reference: [Issue 836](https://github.com/longhorn/longhorn/issues/836) + +Please check the following form to track the impacted version. +| Harvester Version | Longhorn Version | Impacted by Filesystem Trim | +|-------------------|------------------|-----------------------------| +| v1.2.0 | v1.4.3 | Yes | +| v1.2.1 | v1.4.3 | Yes | +| v1.2.2 | v1.5.5 | No | +| v1.3.0 | v1.6.0 | Yes | +| v1.3.1 (upcoming) | v1.6.2 | No | + +If you use the impacted version, please follow the instructions below to mitigate the risk. +::: + Filesystem trim is a common way to release unused space in a filesystem. However, this operation is known to cause IO errors when used with Longhorn volumes that are rebuilding. For more information about the errors, see the following issues: - Harvester: [Issue 4793](https://github.com/harvester/harvester/issues/4739)