Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge 2768, build in packit #2784

Closed
wants to merge 6 commits into from
Closed

Conversation

pcahyna
Copy link
Member

@pcahyna pcahyna commented Apr 4, 2022

No description provided.

jsmeix and others added 6 commits March 8, 2022 15:59
In layout/save/GNU/Linux/210_raid_layout.sh
fixed the RAID10 layout support code as far as possible for now.
Currently only 'near=...' support is (and was) implemented, cf.
rear@4dbbb28
This fix was triggered by ShellCheck
SC2034: param appears unused. Verify use (or export if used externally)
https://github.com/koalaman/shellcheck/wiki/SC2034
SC2066: Since you double quoted this, it will not word split, and the loop will only run once
https://github.com/koalaman/shellcheck/wiki/SC2066
cf. rear#1040 (comment)
Again support RAID10 "far" and "offset" layouts.
Currently if there is more than one RAID10 layout value
only the first one is used because according to
https://unix.stackexchange.com/questions/280283/is-it-possible-to-create-a-mdadm-raid10-with-both-near-and-far-layout-options
it seems it is not possible (or it does not make sense in practice)
to set both "near=..." and "far=..." and we also assume it is not possible
(or it does not make sense in practice) to set more than one RAID10 layout value
because we I don't know what would be the mdadm command to create them, cf.
rear#2768 (comment)
Do an initial general test first of all and not somewhere later in between other code.
@pcahyna
Copy link
Member Author

pcahyna commented Apr 4, 2022

sorry, bad PR.

@pcahyna pcahyna closed this Apr 4, 2022
@jsmeix jsmeix added won't fix / can't fix / obsolete not ReaR / invalid The root cause is not in the ReaR code or ReaR is misused. labels Apr 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not ReaR / invalid The root cause is not in the ReaR code or ReaR is misused. won't fix / can't fix / obsolete
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants