Bug 1251639
Summary: | [PowerKVM]The md5sum value changed when file transfered after enable/disable multi queues repeatedly | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Shuang Yu <shuyu> |
Component: | qemu-kvm-rhev | Assignee: | David Gibson <dgibson> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.2 | CC: | knoel, michen, qzhang, shuyu, virt-maint, zhengtli |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | ppc64le | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-08-18 18:10:19 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Shuang Yu
2015-08-08 07:17:38 UTC
Are you saying that you have been unable to reproduce with current kernel and qemu? If so, I think we will have to close as INSUFFICIENT_DATA. It's very surprising that the md5sum would change across the transfer with scp, since scp has internal checksumming. A file mismatch in this case would suggest not a network problem, but a problem either reading the disk on the source, or writing the disk on the destination. Unless the mismatch was due simply to a truncation of the files (interrupted transfer). (In reply to David Gibson from comment #6) > Are you saying that you have been unable to reproduce with current kernel > and qemu? If so, I think we will have to close as INSUFFICIENT_DATA. > Yes,I cannot reproduce this issue with the current kernel and qemu. > It's very surprising that the md5sum would change across the transfer with > scp, since scp has internal checksumming. A file mismatch in this case > would suggest not a network problem, but a problem either reading the disk > on the source, or writing the disk on the destination. Unless the mismatch > was due simply to a truncation of the files (interrupted transfer). During the file transfer without any interrupt action. Ok, since it can't be reproduced with the current, packages, I'm closing the bug. |