-
This issue can occur after expanding the cluster's LVM storage in both "active/passive" clusters using a LVM based Filesystem resource as well as an "active/active" GFS2 cluster.
-
On an "active/passive" cluster, the issue would appear after running a
pcs resource
LVM-activate resource fails to start properly after storage expansion
Solution verified - Updated on
Request a new translation or translation update
A translation for your language preference does not exist. Click below to request a translation for your selected language.
Issue
Subscriber Exclusive Content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.