RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Document URL: 

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/global_file_system_2/ch-clustsetup-gfs2

Section Number and Name: 

Chapter 5, bullet 7

Describe the issue: 

This section should include language specifying that the Clustered flag must be enabled on any volumes managed by clvmd to be able to safely activate volume groups concurrently across nodes

Suggestions for improvement: 

The section in question already includes a warning box regarding concurrent storage access. We could add to that something along the lines of

"When managing volumes groups using clvmd to allow for concurrent activate of volumes across multiple nodes, the volume groups MUST have the clustered flag enabled. This flag allows clvmd to identify the volumes it must manage which is what enabled clvmd to maintain lvm metadata continuity. Failure to adhere to this configuration renders the configuration unsupported by Red Hat, and may result in storage corruption and loss of data."

Chapter 5 step 7 is now updated on the Customer Portal:

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html-single/global_file_system_2/#ch-clustsetup-GFS2