Does anyone know the magical method in which OVM Manager filters out which phy disk devices it supports for server pool fs?
We want to use CORAID (ATA over Ethernet) storage for our pool fs (we already use it with good success for VM storage). The issue is OVM manager does not treat it as it does with a Fiber channel LUN.
I tried giving the multipath device the same features (specifically 1 queue_if_no_path) but that doesnt seem to be the special sauce.
Has anyone ever dug into this, or heard by the Oracle VM watercooler what it takes for a disk to be eligible to be a POOL FS?
When using the CORAID HBA with the driver (that CORAID has developed for OVM) yes, its a normal shared disk like a FC disk would be treated (the only thing we need to do is tune.ocfs2 to remove the "local" flag on the ocfs2 device.
Bumping this because this is started to get very annoying as OVM Manager keeps treating scsi (/dev/sdX) AoE devices as local storage and not shared (aka Unmanaged Fiberchannel).
Does anyone know what part of OVM Manager or agent is in charge of picking up new sdX or multipath devices and classifying them as Fiberchannel or Local????