On Sat, Apr 18, 2009 at 09:54:38AM +0200, Luca Berra wrote: > because people might want control over what is happening. > otherwise we'll might as well be running windows There is a difference between having to run it *always* manually, or having the choice to do one way (manually) or the other (automantically). Control is not about manuality, control is about having the possibility to do what is considered most convenient. So, the point is not having it automatic, but having the choice between automatic or manual, or both. > 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. Well, so we are on the same frequency! >> The problem is that when something is changed in the array, >> the file needs to be recreated. > no, unless you misconfigure mdadm.conf I did not! :-) >> 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. The cause is "num-devices", which is set by the "--examine --scan" or "--detail --scan". If I grow the array, this changes, and the config file needs an update. Of course, the "num-devices" could be removed, but it is more manual work, which could lead to errors. >> 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 The problem is that the safer information to assemble the array is (or should be) the UUID. Since this is not something easy to remember, it is necessary to find it out. The information could be retrieved from the devices composing it, of course. I find a bit "silly" to have to check the components manually in order to configure the file needed to start the array. Of course, for a fully static environment, this is not a big issue. Once done, is done. For a more "changing" situation, this could be quite annoying and error prone. I already had "booting" issue, because I forgot to *update* the file. In other words, it would be nice to have some more automatic method to handle this configuration file. This should *not* replace the manual operation, it should just be an add on to it. Of course, an "udev" solution would be also good, so I'm not proposing anything different from what is discussed here. As I wrote, these are only my two cents or less. bye, -- piergiorgio -- 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
