On Tue, 2013-12-10 at 13:39 +0100, Henrik Goldman wrote: > > 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. The permanent fix will be functionally identical for the block_size=512 case as the recommended workaround. > I assume it needs to go through the > entire kernel-development cycle before it really becomes mainstream. > Nope, a bugfix like this can go into as soon as the subsystem maintainer signs off on it. > I assume that whenever we see this warning it means that the data > wasn't really written to the array, correct? > That is correct. --nab -- 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
