Description of problem: when using a LVM LogicalVolume as LocalVolume devicePath [0]. Sample config below (where /dev/elasticsearch/elasticsearch is the LVM LogicalVolume):

$ oc get localvolume -n local-storage es-disks -o json | jq .spec.storageClassDevices
[
  {
    "devicePaths": [
      "/dev/elasticsearch/elasticsearch"
    ],
    "fsType": "ext4",
    "storageClassName": "es-disks",
    "volumeMode": "Filesystem"
  }
]

This ends up 

Version-Release number of selected component (if applicable):

Actual results:
- The LocalVolume PV points to an underlying /mnt/local-storage/${StorageClassName}/dm-X path, instead of the /dev/elasticsearch/elasticsearch LogicalVolume.
- /dev/elasticsearch/elasticsearch has different /mnt/local-storage/${StorageClassName}/dm-X symlinks pointing to the same /dev/elasticsearch/elasticsearch LogicalVolume
- Different PersistentVolumes can be provisioned pointing to different /mnt/local-storage/${StorageClassName}/dm-X symlinks, under the same /dev/elasticsearch/elasticsearch LogicalVolume, pointing to the same underlying data.

Expected results:
- Have one and only PV per LocalVolume object.

Additional info:
- Logs dumps and outputs to follow.

---
[0] https://github.com/openshift/local-storage-operator/blob/release-4.5/deploy/cr.yaml#L10