I'm obviously missing something... If chunk size is a stride, why is the /sys/block/md*/queue/max_*sectors_kb being inherited from one of the underlying devices rather than being set to the chunk size or the drive multiple of their max sector settings? Or, in other words, would the chunk size setting have a natural upper bound/limit of one of the drives max_sectors, or the sum of all of the constituent drives max sectors? Thanks, Chris -- 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