From 87d41f5ea147d91007b2c741bffba997bd872a87 Mon Sep 17 00:00:00 2001 From: freeze <1615081+Vicente-Cheng@users.noreply.github.com> Date: Tue, 5 Mar 2024 15:40:07 +0800 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Jillian --- kb/2024-01-30/the_potential_risk_with_fstrim.md | 4 ++-- 1 file changed, 2 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 57952b19..fe469c1b 100644 --- a/kb/2024-01-30/the_potential_risk_with_fstrim.md +++ b/kb/2024-01-30/the_potential_risk_with_fstrim.md @@ -1,5 +1,5 @@ --- -title: The Potential Risk with Fstrim +title: Mitigating fstrim Risk description: The potential risk with fstrim and how to avoid it slug: the_potential_risk_with_fstrim authors: @@ -48,7 +48,7 @@ You can determine if fstrim is enabled in VMs that use affected Longhorn volumes systemctl disable fstrim.timer ``` - Or modify the service file to prevent simultaneous fstrim execution. The service file is located at `/usr/lib/systemd/system/fstrim.timer`. You can modify the file as follows: + To prevent simultaneous fstrim execution, use the following values in the service file (located at `/usr/lib/systemd/system/fstrim.timer`): ``` [Timer] OnCalendar=weekly