> Hi, > > if I understood it correctly, in order to detect > the several array parameters (number of disks, for > example), it is possible to use "mdadm -D /dev/mdX" > or to check the files in the corresponding /sys/block/... > /mdX/... files. Yes, but only if the array is assembled. If not, it's "-E", not "-D", and the target is a member device, not the array. > Now, assuming something needs to be done in scripts, > what would be the best way? Using "mdadm -D ... | grep" > (or "mdadm ... | gawk ...."), or to read the proper > files in /sys/block/md...? That depends on what you need to do. If you need to obtain in depth information about the array and / or act only upon specific contents of a line in the output, then you need to use gawk. If your script merely takes action based upon the existence of some meta-content of the output, then grep or even grep -q may be the better choice. > Assuming the wanted information is available on both > sides, which does not seem always the case. I don't know what you mean by "both sides". -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
