HPE Morpheus VM Essentials
1822895 Members
3578 Online
109645 Solutions
New Discussion

Unable to add a GFS2 Data store to a 3 node VME Cluster (VME 8.0.5 / Ubuntu 24.04.2)

 
Balazs_Szucs
Established Member

Unable to add a GFS2 Data store to a 3 node VME Cluster (VME 8.0.5 / Ubuntu 24.04.2)

Hi all,

I currently set up a 3 node VME Cluster with Synergy bodes booting from Alletra 5030 via FC. I've created LUNs on the Alletra and gave data access to all 3 hosts.

When I try to add a Data Store to the cluster (Infrastructure/Clusters/<mycluster>) I can see all the LUNs provided via FC but nothing happens when I select one of them and hit save.

VME_Datastore.png

In the Administration/Helath/Morpheus logs page I see this:

HPE VME Datastore fail.png

One of the hosts (which runs the vmem vm) I see in the log (/var/log/morpheus-node/morhpd/current):

2025-05-19_08:24:07.85810 08:24:07.858 [pool-3-thread-2] INFO com.morpheus.agent.stats.KvmVmStats - Setting Max Storage: 107374182400
2025-05-19_08:24:37.86423 08:24:37.864 [pool-3-thread-3] INFO com.morpheus.agent.stats.KvmVmStats - Setting Max Storage: 107374182400
2025-05-19_08:25:07.87656 08:25:07.876 [pool-3-thread-5] INFO com.morpheus.agent.stats.KvmVmStats - Setting Max Storage: 107374182400

However on an other host (part of the cluster) I see this in the log:

2025-05-19_08:28:43.67917 device-mapper: create ioctl on 231420fd9bf02d5ea6c9ce9007514b84e1 part1-mpath-231420fd9bf02d5ea6c9ce9007514b84e failed: Device or resource busy
2025-05-19_08:28:43.67917 device-mapper: create ioctl on 28b6c00d2db52c5786c9ce9007514b84e1 part1-mpath-28b6c00d2db52c5786c9ce9007514b84e failed: Device or resource busy
2025-05-19_08:28:43.67918 device-mapper: create ioctl on 28b6c00d2db52c5786c9ce9007514b84e2 part2-mpath-28b6c00d2db52c5786c9ce9007514b84e failed: Device or resource busy
2025-05-19_08:28:43.67918 device-mapper: create ioctl on 28b6c00d2db52c5786c9ce9007514b84e3 part3-mpath-28b6c00d2db52c5786c9ce9007514b84e failed: Device or resource busy

Interestingly this device mapper links to the Boot Volume of the host provided from the Alletra via FC.

What should I check to let it work as intended? I'm out of what log files should I check.

Any insight is very welcome here, thanks!