On Thursday March 17, paul.clements@xxxxxxxxxxxx wrote:
These three patches provide the ability to perform asynchronous writes with raid1. The asynchronous write capability is primarily useful when raid1 is employed in network replication (i.e., with one or more of the disks located on a remote system). It allows us to acknowledge writes before they reach the remote system, thus making much more efficient use of the network.
However I would like to leave them until I'm completely happy with the bitmap resync, including - storing bitmap near superblock (I have this working)
Great. I assume you're using the 64k after the superblock for this (well, with v1 supers, I guess the bitmap could be just about anywhere?). So does this mean there would be multiple copies of the bitmap, or are you simply choosing one disk to which the bitmap is written?
- hot-add bitmap (I've started on this)
I assume this means the ability to add a bitmap to an active array that has no bitmap? Might it also include the ability to modify the bitmap (from userland) while the array is active, as this functionality is desirable to have (perhaps you followed the thread where this was discussed?).
- support for raid5/6 and hopefully raid10. (still to come)
That would be nice too.
and I would really like only-kick-drives-on-write-errors-not-read-errors
Perhaps I can help out with this. I've seen the recent discussions/patches for this, but so far it doesn't look like we have a completely up-to-date/working/tested patch against the latest kernel, do we? So maybe I could do this (unless someone else is already)?
to be the next priority. After that, I will definitely look at async writes.
Great. Thanks.
-- Paul - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
