aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAlex Auvolat <alex@adnab.me>2023-09-07 13:49:12 +0200
committerAlex Auvolat <alex@adnab.me>2023-09-07 13:49:12 +0200
commit6a067e30ee51d3ea9874e3ce18670c39edfd665b (patch)
tree8d116ddb3b8e3531f78219184367447e29a4dfa2
parent6b008b5bd3843bb236f94a1b4472de11f5755f04 (diff)
downloadgarage-6a067e30ee51d3ea9874e3ce18670c39edfd665b.tar.gz
garage-6a067e30ee51d3ea9874e3ce18670c39edfd665b.zip
doc: documentation of rebalance repair
-rw-r--r--doc/book/operations/durability-repairs.md10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/book/operations/durability-repairs.md b/doc/book/operations/durability-repairs.md
index 498c8fda..33130952 100644
--- a/doc/book/operations/durability-repairs.md
+++ b/doc/book/operations/durability-repairs.md
@@ -91,6 +91,16 @@ 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
+
+In [multi-HDD setups](@/documentation/operations/multi-hdd.md), to ensure that
+data blocks are well balanced between storage locations, you may run a
+rebalance operation using `garage repair rebalance`. This is usefull when
+adding storage locations or when capacities of the storage locations have been
+changed. Once this is finished, Garage will know for each block of a single
+possible location where it can be, which can increase access speed. This
+operation will also move out all data from locations marked as read-only.
+
# Metadata operations