On 06/02/2013 11:14 PM, Dan Williams wrote: > On Sun, Jun 2, 2013 at 11:06 PM, H. Peter Anvin <hpa@xxxxxxxxx> wrote: >> On 06/02/2013 10:47 PM, Dan Williams wrote: >>> >>> One hack to prove this may be to explicitly disable write_same before >>> the array is assembled: >>> >>> for i in /sys/class/scsi_disk/*/max_write_same_blocks; do echo 0 > $i; done >>> >>> If this works then maybe md needs to be tolerant of write_same >>> failures since the block layer will simply retry with zeroes. >>> >> >> Trying that (array is already assembled but is currently functional.) >> Let's hope it works. >> > > If I'm reading things correctly that may still result in failure since > md will still pass the REQ_WRITE_SAME bios down to the the devices and > will receive BLK_PREP_KILL for its trouble. md only notices that > write same is disabled on underlying devices at assembly time. > Hmmm... that means getting dracut/udev to supply this little mod, unless it can be fed as a kernel command-line option somehow. Digging... -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
