On Fri, May 16, 2008 at 09:35:44PM +0200, christophe varoqui wrote: > fact: device-mapper refuse to load a RW multipath table on these paths > (ie without libdevmapper:set_task_set_ro()) > question: should change this behaviour to allow to load a RW multipath > table on these paths and let the IO be failed by the storage hardware ? Yes. But relax this *only* for multipath targets, where the whole idea is to "hide" path problems from the layer above. It would not make sense in my view to do this for other DM targets. > Alasdair proposed to add more explicit table loading ioctl return code > when the failure is due to this ready-only paths issue (E_ROFS for > example). I think this should be done too (for non-multipath and other errors). Alasdair -- agk@xxxxxxxxxx -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
