On 06/11/2013 09:47 AM, Joe Lawrence wrote: > > You've probably worked around this by now, but Dan's suggestion can be > tweaked if you are willing to fail/remove/re-add one of the disks. I > just verified the following: > > /sys/block/md125/queue/write_same_max_bytes: 524288 > > % mdadm --fail /dev/md125 /dev/sds1 > % mdadm --remove /dev/md125 /dev/sds1 > % echo 0 > /sys/class/scsi_disk/2\:0\:2\:0/max_write_same_blocks > % mdadm --add /dev/md125 /dev/sds1 > > /sys/block/md125/queue/write_same_max_bytes: 0 > > That gets raid10.c to invoke disk_stack_limits (via raid10_add_disk) > which will recalculate write_same_max_bytes for the MD. > No thanks. I just hacked the kernel directly. -hpa -- 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
