Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionRobert Peterson
2016-07-14 14:06:54 UTC
Document URL:
The GFS2 manual
Section Number and Name:
Describe the issue:
Suggestions for improvement:
A customer recently came to us with a Severity 1 problem related
to using GFS2 shared file system in a virtual machine. The file
system could be seen and mounted from both nodes in the cluster.
If node A created a file, it was seen by node B. If node B created
a file, it was NOT seen by node A.
Upon further analysis, it was discovered that blocks written to the
journal by node B, were not even seen by node A. This indicated the
problem was not at the GFS2 layer, but a layer below.
The problem was that the customer had not properly configured their
vm storage settings on one node. The customer had:
<driver name='qemu' type='raw'/>
When it should have been:
<driver name='qemu' type='raw' cache='none' io='native'/>
When the configuration was changed to add the missing options,
and the virt restarted, GFS2 behaved normally.
Additional information:
Fix with command: virsh edit <vmname>
(I'm a GFS2 file system guy, not a virt expert, so sorry if I'm
a little fuzzy on all this.)
Document URL: The GFS2 manual Section Number and Name: Describe the issue: Suggestions for improvement: A customer recently came to us with a Severity 1 problem related to using GFS2 shared file system in a virtual machine. The file system could be seen and mounted from both nodes in the cluster. If node A created a file, it was seen by node B. If node B created a file, it was NOT seen by node A. Upon further analysis, it was discovered that blocks written to the journal by node B, were not even seen by node A. This indicated the problem was not at the GFS2 layer, but a layer below. The problem was that the customer had not properly configured their vm storage settings on one node. The customer had: <driver name='qemu' type='raw'/> When it should have been: <driver name='qemu' type='raw' cache='none' io='native'/> When the configuration was changed to add the missing options, and the virt restarted, GFS2 behaved normally. Additional information: Fix with command: virsh edit <vmname> (I'm a GFS2 file system guy, not a virt expert, so sorry if I'm a little fuzzy on all this.)