On Mon, Sep 17, 2012 at 03:44:29PM -0400, David Jeffery wrote: > Instead of setting to defaults, how about maintaining previous limits? > The initial queue setup sets defaults when a queue is first configured, > and this maintains known, working limits if all paths are temporarly > lost. For example, I have a test setup with a lower than normal max > segment list. It can fail a test with the previous patch as the > default limits exceed the hardware limits. But this setup will work if > we leave queue limits unchanged in the special case of there being no > target devices. Firstly, the problem cannot be fixed completely - so let's make sure the patch header doesn't claim that, and does explain how different situations are handled and why. Secondly, it's a mpath problem, so the solution should be a patch to dm-mpath that does NOT change the way any non-mpath dm devices are handled. Now my question is whether this can be fixed adequately within the existing interface, or whether userspace needs the ability to control whether limits are reset or not (either by message or ioctl flag). Alasdair -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
