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.

fail to reproduce this bug.
My steps are:
1. build vdo volume on a raw device
2. mount that vdo volume and build GlusterFS volume upon vdo
3. add this glusterfs volume to rhvm as storage domain
4. add a rhel guest vm and use it as template
5. use the template to create multiple vms
6. start those vms and do fio

Is there anything different from your approach, thanks.

Hi Lyu,

This was pretty much the same I did with the above mentioned component versions.

Thanks

Bipin, have you been able to reproduce this again? Or should we close this bug?

Sahina,

I havent seen this yet. You can close for now. Will reopen if i see this again

Closing this as the bug could not be reproduced. Please reopen if this is hit again