Hide Forgot
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
This was recently done on the upstream master branches, so it should be fairly straightforward backports to rhel7-branch of blivet, pykickstart, and anaconda.
Do we have any update on an ETA for this?
Clearing needinfo based on comment 6.
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.
Fix is available in a pull request: https://github.com/rhinstaller/anaconda/pull/1000
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