Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1332316 - RFE:Request for RHEL 6/7 Anaconda option for RAID chunk size
RFE:Request for RHEL 6/7 Anaconda option for RAID chunk size
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda (Show other bugs)
7.2
x86_64 Linux
high Severity high
: rc
: 7.3
Assigned To: Vendula Poncova
Release Test Team
Filip Hanzelka
: FutureFeature
Depends On:
Blocks: 1298243 1395321 1405141 1405142 1428463 1428464
  Show dependency treegraph
 
Reported: 2016-05-02 18:11 EDT by jcastran
Modified: 2017-08-01 08:22 EDT (History)
10 users (show)

See Also:
Fixed In Version: anaconda-21.48.22.105-1
Doc Type: Enhancement
Doc Text:
*Anaconda* enables users to set RAID chunk size This update allows the user to set the "--chunksize" parameter for the "raid" utility in a kickstart file to specify the chunk size of a RAID storage, in KiB. Using the "--chunksize" parameter overrides the default one. As a result, the new chunk size can prevent a negative performance impact the default value might have.
Story Points: ---
Clone Of:
: 1405141 1405142 1428463 (view as bug list)
Environment:
Last Closed: 2017-08-01 04:50:51 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2293 normal SHIPPED_LIVE anaconda bug fix and enhancement update 2017-08-01 08:39:44 EDT

  None (edit)
Description jcastran 2016-05-02 18:11:34 EDT
1. Proposed title of this feature request
   RFE:Request for RHEL 6/7 Anaconda option for RAID chunk size

2. Who is the customer behind the request?
   Account name: (1464305) Shell Information Technology International
   SRM customer: no
   TAM customer: yes
   Strategic Customer: yes
 
3. What is the nature and description of the request?
   I would like to have anaconda extended so that the chunk size can be specified with a kickstart file option.  

 
4. Why does the customer need this?
   We currently are forced to create a partition after installation so that we can get a chunk size that performs significantly better with our data usage.
 
5. How would the customer like to achieve this?
   Include the option in the Red Hat installer environment
 
6. How Red Hat and the customer can test to confirm the requirement is successfully implemented.
   
 
7. Is there already an existing RFE upstream or in Red Hat bugzilla?
   No
 
8. Does the customer have any specific timeline dependencies?
   ASAP
 
9. Is the sales team involved in this request and do they have any additional input?
   No
 
10. List any affected packages or components.
    Raid
 
11. Would the customer be able to assist in testing this functionality if implemented?
    Possibly
Comment 2 David Lehman 2016-05-04 12:00:05 EDT
This was recently done on the upstream master branches, so it should be fairly straightforward backports to rhel7-branch of blivet, pykickstart, and anaconda.
Comment 3 Rob Marti 2016-10-12 22:36:52 EDT
Do we have any update on an ETA for this?
Comment 7 Samantha N. Bueno 2017-01-16 04:29:25 EST
Clearing needinfo based on comment 6.
Comment 8 Gordon Messmer 2017-01-18 17:08:46 EST
In support of this request, I'd like to note that I've measured significantly better performance of 64k chunks under software RAID5 volumes, compared to the default 512k chunks.

https://plus.google.com/+GordonMessmer/posts/H5DuyP1LHPU?sfc=false
https://plus.google.com/+GordonMessmer/posts/eSe6iNmk1Fs?sfc=false

In addition to an option, I'd really like to see the default chunk size changed to 64k for parity RAID levels.
Comment 10 Vendula Poncova 2017-03-21 05:27:41 EDT
Fix is available in a pull request: https://github.com/rhinstaller/anaconda/pull/1000
Comment 15 errata-xmlrpc 2017-08-01 04:50:51 EDT
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.

https://access.redhat.com/errata/RHBA-2017:2293

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