Skip to content
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.

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

RAIDZ: rephrase write section #509

Merged
merged 1 commit into from
Jun 4, 2024
Merged

Conversation

gmelikov
Copy link
Member

@gmelikov gmelikov commented Jun 3, 2024

Closes: #508

Because of full stripe width, one block write will write stripe part on each disk.
One RAIDZ vdev has a write IOPS of one slowest disk because of that in worst case.
A stripe spans across all drives in the array. A one block write will write the stripe part onto each disk.
A RAIDZ vdev has a write IOPS of the slowest disk in the array in the worst case because write operation of all stripe parts must be completed on each disk.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A RAIDZ vdev has a write IOPS of the slowest disk in the array in the worst case because the write operation of all stripe parts must be completed on each disk.

Closes: openzfs#508
Signed-off-by: George Melikov <mail@gmelikov.ru>
@gmelikov gmelikov merged commit 60c078f into openzfs:master Jun 4, 2024
1 check failed
@gmelikov gmelikov deleted the raidz_wording branch June 4, 2024 09:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Can someone please decipher this?
2 participants