Incorect :
A. Debian cere explicit mdadm.conf
https://wiki.debian.org/SoftwareRAID
Cindva am mai avut discutia asta, s-a reintrodus necesitatea de a avea
mdadm.conf pentru un motiv anume, momentan nu gasesc detaliile tehnice,
mai caut.
B. RHEL/Centos 5 si 6 (nu am testat inca pe 7)
RHEL5 cere explicit mdadm.conf, conform documentatiei
RHEL6 se comporta astfel : Daca faci array cu metadate 1.x post
instalare si nu le treci in mdadm.conf, dupa urmatorul reboot deviceul
este detectat drept md127, este inutilizabil si nici nu se
sincronizeaza. Arata asa :
Personalities : [raid1]
md127 : active (auto-read-only) raid1 sdc1[1] sdb1[0]
488252928 blocks super 1.2 [2/2] [UU]
resync=PENDING
bitmap: 4/4 pages [16KB], 65536KB chunk
Conform linkului tau, :
Version 1.2 superblocks will not automatically assemble with a numbered
device name unless specifically told to do so. There are two way to do
this:
1. Pass the --name=<number> option to the mdadm --create command. This
will cause the name to be a simple number, and mdadm will assume that
you want the array created with that number as the device name. Aka, 0
will get assembled as /dev/md0, 1 as /dev/md1, etc.
-> Nu functioneaza
2. Create an ARRAY line in the mdadm.conf file that specifies the uuid
of the array and the name you wish the array to have
-> asta este fix ca am recomandat eu initial, si functioneaza.
_______________________________________________
RLUG mailing list
[email protected]
http://lists.lug.ro/mailman/listinfo/rlug
