Description of problem: Refresh the "rhs_system_init" script in /usr/lib/glusterfs/.unsupported folder to accommodate the new recommendations. Version-Release number of selected component (if applicable): RHSS 3.0.3 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Document URL: Section Number and Name: Describe the issue: Suggestions for improvement: Additional information: Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 958653 [details] Performance Team Recommendations for setting up RHSS bricks
Created attachment 963891 [details] rhs-system-init.sh diff diff -pruN
Ben few questions here: 1. I see a prompt asking for question, can you force it not to ask that question. If we want to use your script in automation, prompt wouldn't help. WARNING: Converting logical volume RHS_vg1/RHS_pool1 and RHS_vg1/metadata to pool's data and metadata volumes. THIS WILL DESTROY CONTENT OF LOGICAL VOLUME (filesystem etc.) Do you really want to convert RHS_vg1/RHS_pool1 and RHS_vg1/metadata? [y/n]: 2. The script fails the following error: mkfs.xfs -i size=512 -n size=8192 -d su=128k,sw=10 /dev/RHS_vg1/RHS_lv1 warning: device is not properly aligned /dev/RHS_vg1/RHS_lv1 Use -f to force usage of a misaligned device Can we fix this somehow, since majority of us use VMs for functionality testing with around 50/100GB of disk space. Please find the debug output of the script.
Created attachment 965030 [details] rhs-system-init-debug
I am doing an update now, I'll have a test version shortly to address this.
Ben, I've updated the patch. From the look of it, I think it might error out. Please review.
Submitted patch for review: https://code.engineering.redhat.com/gerrit/#/c/39103/
Verified with the latest build. The issues stated in comment 7 are resolved, marking as verified. However, question 1 is in comment 7 is not addressed intentionally.
Ben, This bug has been added to 3.0.3 errata. Please set the "requires_doc_text" field appropriately? If set to "?", do provide the doc text in the Doc Text field. Thanks, Divya
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://rhn.redhat.com/errata/RHBA-2015-0038.html