From d1333c172939d8d29d09c939e68c270458ef68c5 Mon Sep 17 00:00:00 2001 From: Agathe Porte Date: Tue, 14 Jul 2026 21:12:45 +0000 Subject: [PATCH] doc: multi-hdd: refer to rebalance op (#1491) The rebalance op links to the multi-hdd page, but the multi-hdd page does not refer to the rebalance op description and only states that an operator can launch a repair procedure without stating which procedure. Add a link to the rebalance repair procedure in the multi-hdd page to make it easier to find what procedure to run for rebalance. Reviewed-on: https://git.deuxfleurs.fr/Deuxfleurs/garage/pulls/1491 --- doc/book/operations/durability-repairs.md | 2 +- doc/book/operations/multi-hdd.md | 9 +++++---- 2 files changed, 6 insertions(+), 5 deletions(-) diff --git a/doc/book/operations/durability-repairs.md b/doc/book/operations/durability-repairs.md index 8a307c84..af7df745 100644 --- a/doc/book/operations/durability-repairs.md +++ b/doc/book/operations/durability-repairs.md @@ -91,7 +91,7 @@ is definitely lost, then there is no other choice than to declare your S3 object as unrecoverable, and to delete them properly from the data store. This can be done using the `garage block purge` command. -## Rebalancing data directories +## Rebalancing data directories {#rebalance} In [multi-HDD setups](@/documentation/operations/multi-hdd.md), to ensure that data blocks are well balanced between storage locations, you may run a diff --git a/doc/book/operations/multi-hdd.md b/doc/book/operations/multi-hdd.md index c21b73d7..f9366a82 100644 --- a/doc/book/operations/multi-hdd.md +++ b/doc/book/operations/multi-hdd.md @@ -68,10 +68,11 @@ To rebalance data, two strategies can be used: secondary directory. This might never end up rebalancing everything if there are data blocks that are only read and never written. -- Active rebalancing: an operator of a Garage node can explicitly launch a repair - procedure that rebalances the data directories, moving all blocks to their - primary location. Once done, all secondary locations for all hash slices are - removed so that they won't be checked anymore when looking for a data block. +- Active rebalancing: an operator of a Garage node can [explicitly launch a + repair procedure](@/documentation/operations/durability-repairs.md#rebalance) + that rebalances the data directories, moving all blocks to their primary + location. Once done, all secondary locations for all hash slices are removed + so that they won't be checked anymore when looking for a data block. ## Read-only storage locations