Bug 736666
Summary: | v7 storage test has an improper write/read sequence | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Hardware Certification Program | Reporter: | WANG Chao <chaowang> | ||||
Component: | Test Suite (tests) | Assignee: | Greg Nichols <gnichols> | ||||
Status: | CLOSED ERRATA | QA Contact: | Guangze Bai <gbai> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 6.1 | CC: | chaowang, czhang, fge, gbai, rlandry, ruyang, ykun, yshao | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: |
In v7 1.3, storage test didn't do read/write testing in correct sequence, which was like:
write with 1024 bytes;
write with 2048 bytes;
...
write with 65536 bytes.
read with 1024 bytes;
read with 2048 bytes;
...
read with 65536 bytes.
The writing testing would never verify the data because the old data was always overridden by subsequent writing operation.
In v7 1.4, this issue has been fixed, now the read/write sequence is like this:
write with 1024 bytes; read with 1024 bytes and verifying;
write with 2048 bytes; read with 2048 bytes and verifying;
...
write with 65536 bytes, read with 65536 bytes and verifying.
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2011-11-08 15:43: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: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
WANG Chao
2011-09-08 11:43:01 UTC
Created attachment 522105 [details] patch fix This patch also fix: bug 736638 , bug 736675 and bug 736679 Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: In v7 1.3, storage test didn't do read/write testing in correct sequence, which was like: write with 1024 bytes; write with 2048 bytes; ... write with 65536 bytes. read with 1024 bytes; read with 2048 bytes; ... read with 65536 bytes. The writing testing would never verify the data because the old data was always overridden by subsequent writing operation. In v7 1.4, this issue has been fixed, now the read/write sequence is like this: write with 1024 bytes; read with 1024 bytes and verifying; write with 2048 bytes; read with 2048 bytes and verifying; ... write with 65536 bytes, read with 65536 bytes and verifying. 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. http://rhn.redhat.com/errata/RHBA-2011-1436.html 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. http://rhn.redhat.com/errata/RHBA-2011-1436.html |