Cause: Using partitions for the the --block.db and --block.wal arguments of the ceph-volume lvm create command. The db and wal options for the `lvm_volumes` config option in ceph-ansible is used to set those arguments during a deployment. Consequence: Occasionally the OSD will not start because udev resets the partitions permissions back to root:disk after creation by ceph-volume. Workaround (if any): Start the ceph-volume systemd unit manually for the failed OSD. For example, if the failed OSD has an ID of 8 the workaround would be running `systemctl start 'ceph-volume@lvm-8-*'`. If you know the failed OSDs UUID as well you can use the service command: `service ceph-volume@lvm-8-4c6ddc44-9037-477d-903c-63b5a789ade5 start`, where 4c6ddc44-9037-477d-903c-63b5a789ade5 is the UUID for osd.8. Result: Permissions on the partitions affected would be changed back to ceph:ceph and the OSD will be restarted and join the cluster.