Skip to content

RAIDZ.rst #477

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Dec 13, 2023
Merged

RAIDZ.rst #477

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a150af2
Calculation error
jameskimmel Dec 4, 2023
af6adae
parity.rst
jameskimmel Dec 4, 2023
c819eff
Update RAIDZ.rst
jameskimmel Dec 4, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions docs/Basic Concepts/RAIDZ.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@ we will allocate on disk:

- one 4K block of data

- one 4K padding block
- one 4K parity block

and usable space ratio will be 50%, same as with double mirror.

Expand All @@ -62,7 +62,9 @@ Another example for ``ashift=12`` and ``recordsize=128K`` for raidz1 of 3 disks:

- one stripe can have up to 2 data parts of 4K size because of 1 parity blocks

- we will have 128K/2 = 64 stripes with 8K of data and 4K of parity each
- we will have 128K/8k = 16 stripes with 8K of data and 4K of parity each

- 16 stripes each with 12k, means we write 192k to store 128k

so usable space ratio in this case will be 66%.

Expand Down