Bug 1210296
| Summary: | [RFE]Gluster - Data Alignment value should be defaulted to 256K when user tries to create a gluster brick using RAID0 volume or JBOD Disk from Ovirt | ||
|---|---|---|---|
| Product: | [oVirt] vdsm | Reporter: | RamaKasturi <knarra> |
| Component: | General | Assignee: | Timothy Asir <tjeyasin> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | RamaKasturi <knarra> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | --- | CC: | bazulay, bmcclain, bugs, gklein, lsurette, mgoldboi, pstehlik, rbalakri, rnachimu, sabose, sankarshan, srevivo, tjeyasin, ykaul |
| Target Milestone: | ovirt-4.0.0-alpha | Keywords: | FutureFeature |
| Target Release: | 4.18.0 | Flags: | ylavi:
ovirt-4.0.0?
bmcclain: planning_ack+ rule-engine: devel_ack+ rule-engine: testing_ack? |
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-08-22 06:02:37 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Gluster | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1187461 | ||
|
Description
RamaKasturi
2015-04-09 11:37:08 UTC
We don't need to ask the strip size for RAID0 volume from the user. We can default the data alignment value to 256K internally. Refer the Redhat Storage Admin Guide for more info : https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3/html/Administration_Guide/Brick_Configuration.html Aggregation of disks in RAID0 volume is not recommended by gluster. So we can expect the user to create RAID0 volume using only one disk. Patch sent to upstream for review: https://gerrit.ovirt.org/40890 Earlier assumption of the default alignment value is zero. But now its changed to 256. Alignment value plays an important role for calculation and design making while pvcreate, vg, pool & lv create process. This requires lot of changes in the code and might need to do lot of testing. The patch is under review. We will sent it to downstream after the review is complete and merged upstream. this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015. Please review this bug and if not a blocker, please postpone to a later release. All bugs not postponed on GA release will be automatically re-targeted to - 3.6.1 if severity >= high - 4.0 if severity < high oVirt 3.6.0 has been released on November 4th, re-targeting to 4.0 since this bug has been marked with severity < high This bug is flagged for 3.6, yet the milestone is for 4.0 version, therefore the milestone has been reset. Please set the correct milestone or add the flag. This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions The patch fixing this is merged in master. Moving to ON_QA to verify with 4.0 build Closing due to capacity reasons, if still happen, please reopen. |