Bug 1298886

Summary: [abrt] qemu-img: get_block_status(): qemu-img killed by SIGABRT
Product: Red Hat Enterprise Linux 7 Reporter: Miroslav Rezanina <mrezanin>
Component: qemu-kvm-rhevAssignee: Hanna Czenczek <hreitz>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 7.2CC: chayang, derez, hreitz, huding, jkurik, juzhang, knoel, kwolf, mrezanin, nsoffer, rbalakri, sherold, virt-bugs, virt-maint, weliao, xfu, ykaul
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Fixed In Version: qemu-kvm-rhev-2.5.0-1.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1283116
: 1299345 (view as bug list) Environment:
Last Closed: 2016-11-07 20:55:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1283278, 1299345, 1327592    

Comment 3 Ademar Reis 2016-05-31 19:22:26 UTC
*** Bug 1290683 has been marked as a duplicate of this bug. ***

Comment 4 weliao 2016-06-01 02:09:10 UTC
Reproduced this bug with qemu-img-rhev-2.3.0-31.el7.x86_64 & qemu-kvm-rhev-2.3.0-31.el7.x86_64

[root@dhcp-8-118 qemu230]# truncate -s 1G test_sparse
[root@dhcp-8-118 qemu230]# echo "a" >> test_sparse
[root@dhcp-8-118 qemu230]# qemu-img map test_sparse
Offset          Length          Mapped to       File
qemu-img: qemu-img.c:2294: get_block_status: Assertion `nb_sectors' failed.
Aborted (core dumped)

Verified the bug with qemu-img-rhev-2.6.0-4.el7.x86_64 & qemu-kvm-rhev-2.6.0-4.el7.x86_64

[root@dhcp-8-118 opt]# truncate -s 1G test_sparse
[root@dhcp-8-118 opt]# echo "a" >> test_sparse
[root@dhcp-8-118 opt]# qemu-img map test_sparse
Offset          Length          Mapped to       File
0x40000000      0x200           0x40000000      test_sparse

according to this result.  The bug is fixed.

Comment 7 errata-xmlrpc 2016-11-07 20:55:01 UTC
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.