On Fri, Apr 17, 2009 at 08:40:14PM +0200, Piergiorgio Sartor wrote:
My two cents on this.
One puzzling thing of mdadm.conf is how it is created.
In order to get it, either "mdadm --detail --scan" or
"mdadm --examine --scan" is required.
If I understand it correctly, the latter uses information
from the underlining disks directly.
exactly
Now, why this command should be run manually?
because people might want control over what is happening.
otherwise we'll might as well be running windows
Can the "system" does it automatically on boot or on hotplug?
on hotplug udev already tries to assemble raid arrays, this is the topic
of the discussion, how to make it just work on your desktop/laptop pc,
and how to make it not break the carefully tuned setup on my server,
where i will probably never connect usb/esata array.
The problem is that when something is changed in the array,
the file needs to be recreated.
no, unless you misconfigure mdadm.conf
For example, this happened to me, after growing the array it
was not possibile anymore to restart it without rerunning
the "--examin --scan" thing.
probably because you left some component device name in the mdadm.conf
file, don't.
It seems to me that the usage of mdadm.conf is a bit
fragile and looping.
To start the array I need mdadm.conf, to create it I
not really
need the array... (maybe alread started).
i dont see the problem
L.
--
Luca Berra -- bluca@xxxxxxxxxx
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
--
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
