diff options
| -rw-r--r-- | doc/book/operations/durability-repairs.md | 1 | ||||
| -rw-r--r-- | doc/book/operations/multi-hdd.md | 5 |
2 files changed, 3 insertions, 3 deletions
diff --git a/doc/book/operations/durability-repairs.md b/doc/book/operations/durability-repairs.md index 33130952..b0d2c78a 100644 --- a/doc/book/operations/durability-repairs.md +++ b/doc/book/operations/durability-repairs.md @@ -124,4 +124,3 @@ in your cluster, you can run one of the following repair procedures: - `garage repair versions`: checks that all versions belong to a non-deleted object, and purges any orphan version - `garage repair block_refs`: checks that all block references belong to a non-deleted object version, and purges any orphan block reference (this will then allow the blocks to be garbage-collected) - diff --git a/doc/book/operations/multi-hdd.md b/doc/book/operations/multi-hdd.md index 5f952262..36445b0a 100644 --- a/doc/book/operations/multi-hdd.md +++ b/doc/book/operations/multi-hdd.md @@ -65,7 +65,8 @@ To rebalance data, two strategies can be used: Garage checks whether the existing copy is in the primary directory of the slice or in a secondary directory. If the current copy is in a secondary directory, Garage re-writes a copy in the primary directory and deletes the one from the - secondary directory. + 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 @@ -94,7 +95,7 @@ it might still contain subdirectories, but no data files. You can check that it contains no files using: ```bash -find -type f /path/to/old_data +find -type f /path/to/old_data # should not print anything ``` at which point it can be removed from the `data_dir` list in your config file. |