From af12f1dd51df7424b0e46afa8cb3dc46ebc798ae Mon Sep 17 00:00:00 2001 From: mcoms Date: Wed, 25 Feb 2026 14:17:59 -0500 Subject: [PATCH] Fix formatting errors in ReFS memory usage recommendation --- .../backup-and-storage/fix-heavy-memory-usage-refs.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/support/windows-server/backup-and-storage/fix-heavy-memory-usage-refs.md b/support/windows-server/backup-and-storage/fix-heavy-memory-usage-refs.md index 539e06f3e4..19ae97bcf6 100644 --- a/support/windows-server/backup-and-storage/fix-heavy-memory-usage-refs.md +++ b/support/windows-server/backup-and-storage/fix-heavy-memory-usage-refs.md @@ -63,8 +63,8 @@ Value Type: **REG_DWORD** ReFS has a lazy MM unmap logic. So when ReFS cycles the entire namespace to complete an MM unmap, it unmaps at a certain granularity. The amount of virtual address space that is unmapped is determined by the following formula: -RefsNumberOfChunksToTrim *128 MB (for volume of size > 10 TB) -RefsNumberOfChunksToTrim* 64 MB (for volume of size < 10 TB) +* `RefsNumberOfChunksToTrim * 128 MB` (for volume of size > 10 TB) +* `RefsNumberOfChunksToTrim * 64 MB` (for volume of size < 10 TB) This option works if the VA range that's being unmapped doesn't have any active references (that is, mapped metadata pages).