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.
Description of problem:
'qemu-io write' to a raw image over libgfapi fails.
Version-Release number of selected component (if applicable):
qemu-kvm-2.12.0-81.module+el8.1.0+3619+dfe1ae01
kernel-4.18.0-112.el8.x86_64
Gluster server:
Version: glusterfs-server-3.12.2-43.el7rhgs
Volume info:
# gluster volume info vol
Volume Name: vol
Type: Distribute
Volume ID: 6b299573-ffed-49c6-8b0f-68602c389085
Status: Started
Snapshot Count: 0
Number of Bricks: 1
Transport-type: tcp
Bricks:
Brick1: gluster-virt-qe-01.lab.eng.pek2.redhat.com:/data/brick1/gv2
Options Reconfigured:
transport.address-family: inet
nfs.disable: on
How reproducible:
100%
Steps to Reproduce:
1.Create a raw image over libgfapi
# qemu-img create -f raw gluster://gluster-virt-qe-01.lab.eng.pek2.redhat.com/vol/test.img 5G
2. Write data in it via 'qemu-io write'
# qemu-io -c 'write 0 1G' -f raw gluster://gluster-virt-qe-01.lab.eng.pek2.redhat.com/vol/test.img
[2019-07-10 11:18:48.190841] E [rpc-clnt.c:346:saved_frames_unwind] (--> /lib64/libglusterfs.so.0(_gf_log_callingfn+0x12f)[0x7fb64f8c9f0f] (--> /lib64/libgfrpc.so.0(+0xdad4)[0x7fb64f66dad4] (--> /lib64/libgfrpc.so.0(+0xdbf2)[0x7fb64f66dbf2] (--> /lib64/libgfrpc.so.0(rpc_clnt_connection_cleanup+0xc5)[0x7fb64f66ebd5] (--> /lib64/libgfrpc.so.0(+0xf7b8)[0x7fb64f66f7b8] ))))) 0-vol-client-0: forced unwinding frame type(GlusterFS 3.3) op(WRITE(13)) called at 2019-07-10 11:18:48.189231 (xid=0xc)
[2019-07-10 11:18:52.063952] I [io-stats.c:4027:fini] 0-vol: io-stats translator unloaded
write failed: Transport endpoint is not connected
Actual results:
Write fails as above.
Expected results:
Write data successfully.
Additional info:
1. For qcow2, write data successfully.
# qemu-img create -f qcow2 gluster://gluster-virt-qe-01.lab.eng.pek2.redhat.com/vol/tt.qcow2 5G
# qemu-io -c 'write 0 1G' gluster://gluster-virt-qe-01.lab.eng.pek2.redhat.com/vol/tt.qcow2
wrote 1073741824/1073741824 bytes at offset 0
1 GiB, 1 ops; 0:00:19.74 (51.869 MiB/sec and 0.0507 ops/sec)
[2019-07-10 11:21:23.416252] I [io-stats.c:4027:fini] 0-vol: io-stats translator unloaded
In fast train, it works normally.
Tested with:
qemu-kvm-4.0.0-5.module+el8.1.0+3622+5812d9bf
Write data to the same image as comment 0:
# qemu-io -c 'write 0 1G' -f raw gluster://gluster-virt-qe-01.lab.eng.pek2.redhat.com/vol/test.img
wrote 1073741824/1073741824 bytes at offset 0
1 GiB, 1 ops; 0:00:23.48 (43.598 MiB/sec and 0.0426 ops/sec)
[2019-07-10 11:25:01.475868] I [io-stats.c:4027:fini] 0-vol: io-stats translator unloaded
# echo $?
0
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2019:3345