Bug 1210296 - [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
Summary: [RFE]Gluster - Data Alignment value should be defaulted to 256K when user tr...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: General
Version: ---
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.0.0-alpha
: 4.18.0
Assignee: Timothy Asir
QA Contact: RamaKasturi
URL:
Whiteboard:
Depends On:
Blocks: rhsc_qe_tracker_everglades
TreeView+ depends on / blocked
 
Reported: 2015-04-09 11:37 UTC by RamaKasturi
Modified: 2016-08-22 06:02 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-22 06:02:37 UTC
oVirt Team: Gluster
Embargoed:
ylavi: ovirt-4.0.0?
bmcclain: planning_ack+
rule-engine: devel_ack+
rule-engine: testing_ack?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1270792 0 high CLOSED console partitioned brick devices are created with incorrect data alignment 2023-09-14 03:06:37 UTC
oVirt gerrit 40890 0 master ABANDONED gluster: set default value for dataalignment and physicalextent value 2015-12-21 09:11:19 UTC
oVirt gerrit 47959 0 None None None 2016-04-12 12:37:48 UTC

Internal Links: 1270792

Description RamaKasturi 2015-04-09 11:37:08 UTC
Description of problem:
As of now when user tries to create a RAID0 volume there is no way for him to specify a stripe size. User should be given an option to specify the stripe size.

Version-Release number of selected component (if applicable):
ovirt-engine-webadmin-portal-3.6.0-0.0.master.20150406175153.gite240701.el6.noarch

How reproducible:


Steps to Reproduce:
1. Add a rhel7 node to console which has JBODS configured with 0.
2. Now sync all the devices in UI.
3. click on the create brick dialog.
4. For RAID0, user is not asked to provide the stripe size.

Actual results:
UI should does not provide a way for the user to specify the stripe size 

Expected results:
UI should provide a way for the user to specify the stripe size for RAID0 and that should be used to tune lvm parameters while creating a brick.

Additional info:

Comment 1 Ramesh N 2015-05-11 10:59:26 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

Comment 2 Ramesh N 2015-05-11 11:03:40 UTC
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.

Comment 3 Timothy Asir 2015-05-13 18:19:33 UTC
Patch sent to upstream for review: https://gerrit.ovirt.org/40890

Comment 4 Timothy Asir 2015-08-25 06:35:58 UTC
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.

Comment 5 Sandro Bonazzola 2015-10-26 12:37:20 UTC
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

Comment 6 Sandro Bonazzola 2015-11-05 08:21:15 UTC
oVirt 3.6.0 has been released on November 4th, re-targeting to 4.0 since this bug has been marked with severity < high

Comment 7 Red Hat Bugzilla Rules Engine 2015-11-16 14:07:44 UTC
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.

Comment 8 Mike McCune 2016-03-28 23:40:50 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 9 Sahina Bose 2016-04-12 12:37:48 UTC
The patch fixing this is merged in master. Moving to ON_QA to verify with 4.0 build

Comment 10 Pavel Stehlik 2016-08-22 06:02:37 UTC
Closing due to capacity reasons, if still happen, please reopen.


Note You need to log in before you can comment on or make changes to this bug.