В Tue, 10 Feb 2015 03:24:28 -0500 Felix Miata <mrmazda@earthlink.net> пишет:
Andrei Borzenkov composed on 2015-02-01 09:13 (UTC+0300):
Felix Miata wrote:
md118 = sda8 + sdb8 label: 1md08tmp md119 = sda9 + sdb9 label: 1md09root1
After completing the YaST2 build process, I installed 13.1 on 1md09root1. This is the (condensed) mdadm.conf installation created, with appended the 2 sda/sdb partitions making up each device:
DEVICE containers partitions ARRAY /dev/md/srv10:md-home UUID=99e6... ARRAY /dev/md/srv10:md-isos UUID=637f... # P17
I'd like to get back the orderly simplicity of md0-md9
Do not use meaningful names then. Use md0 - md9 as name (or possibly simply 0 - 9). X in mdX is device minor number which is allocated at runtime; if array name looks like number, mdadm is using it as minor number; otherwise it allocates one from upper half to reduce possibility of collision.
Too late for that for this particular HD pair, but I have managed to reduce my confusion by including
/dev/mdX metadata=1.0
following ARRAY on each device line in /etc/mdadm.conf, then rebooting the prior kernel, uninstalling the newest kernel, and reinstalling the newest kernel, for the 13.2 and 13.3 installations. For 13.1 I've been a bit less daring, so have only changed mdadm.conf, getting the mdX names I expect for all except the / partition, which in every installation to start with was md127, and remains in 13.1, probably only until the next update kernel arrives.
Is there some what to provide mdadm.conf to the installer, getting the good names from the outset instead of via the convolution I went through?
Not that I am aware of. What is wrong with naming arrays "0", "1" etc? I just verified that you get /dev/md0, /dev/md1, ... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org