| Summary: | sys-fs/mdadm-3.3-r2 - checkarray --all queues the check only for the first array | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Anna Tikhomirova <vamp> |
| Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | UNCONFIRMED --- | ||
| Severity: | normal | CC: | alexander |
| Priority: | Normal | Keywords: | PATCH |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | proposed patch | ||
Confirming this: $ sudo checkarray --all checkarray: I: check queued for array md126. $ sudo checkarray --all --idle checkarray: I: check queued for array md126. checkarray: I: selecting idle I/O scheduling class and 15 niceness for resync of md126. checkarray: I: check queued for array md127. checkarray: I: selecting idle I/O scheduling class and 15 niceness for resync of md127. |
Created attachment 375688 [details] proposed patch sys-fs/mdadm-3.3-r2 introduced checkarray script from the debian patchset. However this script doesn't behave correctly if you have more than one array and start the script with --all argument (or pass multiple arrays in the command line) and without --idle, --slow, --fast or --realtime arguments. For example, just: checkarray --all. In this case, the script queues the check only for the first array from the list. It seems that there is an erroneous 'break', which breaks the whole 'for array in $arrays' loop.