From c26fc5e45a7db3d44288143ca34e9688c80e87f6 Mon Sep 17 00:00:00 2001 From: Johannes Kastl Date: Mon, 27 Jun 2022 15:09:52 +0200 Subject: [PATCH] docs/Administrator-Guide/arbiter-volumes-and-quorum.md: rephrase sentence on arbiter brick disk usage --- docs/Administrator-Guide/arbiter-volumes-and-quorum.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Administrator-Guide/arbiter-volumes-and-quorum.md b/docs/Administrator-Guide/arbiter-volumes-and-quorum.md index c994018..4b87ec2 100644 --- a/docs/Administrator-Guide/arbiter-volumes-and-quorum.md +++ b/docs/Administrator-Guide/arbiter-volumes-and-quorum.md @@ -76,7 +76,7 @@ _client-quorum to 'auto'. This setting is **not** to be changed._ ## Arbiter brick(s) sizing Since the arbiter brick does not store file data, its disk usage will be considerably -less than for the other bricks of the replica. The sizing of the brick will depend on +smaller than for the other bricks of the replica. The sizing of the brick will depend on how many files you plan to store in the volume. A good estimate will be 4KB times the number of files in the replica. Note that the estimate also depends on the inode space allocated by the underlying filesystem for a given disk size.