> A quick work-around here is to increase FD_MAX_SECTORS to 4096 or 8192 > (2MB or 4MB max request size), as with ESX you'll only be using 512 > block_size, so this will be OK. > > I'm considering a couple of difference approaches here for a proper > solution, but changing FD_MAX_SECTOR to a larger value for 512 > block_size should get you up and running. > Thank you. We will try this and report back. The biggest issue is to have a permanent fix though. I assume it needs to go through the entire kernel-development cycle before it really becomes mainstream. I assume that whenever we see this warning it means that the data wasn't really written to the array, correct? -- Henrik -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
