Bug 609779
| Summary: | errors were found on image after cut off host power during iozone running in guest. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Miya Chen <michen> |
| Component: | qemu-kvm | Assignee: | Kevin Wolf <kwolf> |
| Status: | CLOSED NOTABUG | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.0 | CC: | mkenneth, tburke, virt-maint |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-07-01 10:02:55 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Miya Chen
2010-07-01 05:10:19 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion. I've looked it up and this message just means that there are some clusters allocated that are after the end of the file. Probably harmless. This might happen when the clusters have been allocated, but not yet written to. The errors start 11,618,361,344 bytes. To confirm my theory, could you please check if the image file size is just below this value? Also, if you write to the image (maybe you have already written enough by booting it - then the file size would differ, of course), do the qemu-img check errors disappear? (In reply to comment #4) > I've looked it up and this message just means that there are some clusters > allocated that are after the end of the file. Probably harmless. This might > happen when the clusters have been allocated, but not yet written to. > > The errors start 11,618,361,344 bytes. To confirm my theory, could you please > check if the image file size is just below this value? # qemu-img info win2008r2-64.qcow2 image: win2008r2-64.qcow2 file format: qcow2 virtual size: 15G (16106127360 bytes) disk size: 11G cluster_size: 4096 Also, if you write to > the image (maybe you have already written enough by booting it - then the file > size would differ, of course), do the qemu-img check errors disappear? yes, after boot it again, qemu-img check errors disappeared. Great, so your image is fine. Closing as NOTABUG. I'll take care of this case when improving the qemu-img check messages. |