-
Notifications
You must be signed in to change notification settings - Fork 73
description of how reads/writes work in detail #2
base: master
Are you sure you want to change the base?
description of how reads/writes work in detail #2
Conversation
Adding detailed descriptions of the following to the md(4) manpage: * How reads/writes work in detail, especially with respect to the minimum/maximum number of bytes that are always fully read/written. * How reads/writes work when the array is degraded and or when a rebuild takes place. * Some general concepts of how the chunksize affect reads/writes. Signed-off-by: Christoph Anton Mitterer <[email protected]>
Same as before: now directly as pull request. And again, please thoroughly read what I've written and check it for any mistakes! |
Oh and one more thing: |
On Wed, 10 Jul 2013 07:13:46 -0700 Christoph Anton Mitterer
Thanks. Again, it would be easier to reply if the patch was in the email.
Preferred language is English. I don't think above fits.
In general I think this content is probably useful. It need a bit of NeilBrown |
Signed-off-by: Christoph Anton Mitterer <[email protected]>
Signed-off-by: Christoph Anton Mitterer <[email protected]>
Signed-off-by: Christoph Anton Mitterer <[email protected]>
Signed-off-by: Christoph Anton Mitterer <[email protected]>
Signed-off-by: Christoph Anton Mitterer <[email protected]>
Signed-off-by: Christoph Anton Mitterer <[email protected]>
Signed-off-by: Christoph Anton Mitterer <[email protected]>
Signed-off-by: Christoph Anton Mitterer <[email protected]>
@calestyo would you please give a description of how and where the parities are updated in disks? |
Adding detailed descriptions of the following to the md(4) manpage:
minimum/maximum number of bytes that are always fully read/written.
place.
Signed-off-by: Christoph Anton Mitterer [email protected]