On 11/29/2017 12:42 PM, Gandalf Corvotempesta wrote: > 2017-11-29 17:52 GMT+01:00 Phil Turmel <philip@xxxxxxxxxx>: >> These are good reasons. I have also seen reports of NAS devices/distros >> unconditionally partitioning devices that don't have one. Although I >> have in the past used raw devices with mdadm, I don't plan to do so with >> any future systems. > > I always used partitioning. > But last time i've tried to configure mdadm to automatically replace a > disk when replaced: > https://linux.die.net/man/5/mdadm.conf > "POLICY" section, tried all but the best candidate seems to be "spare-same-slot" > > I was never able to make that working. I've tried everything: insert a > brand new disk, insert an already partitioned disks and so on. > I always though that the main issue was due to disk partitioning, > mdadm won't be able to re-add a brand new disks if raid is made > with paritions (the new disks doesn't have any partition) > > Any idea ? I don't let mdadm do any such automatic allocation of new devices. If you have to manually put the device in the server, its only a few seconds more to note which device it is in dmesg, and add it to the array. (And partition it, if not already.) Phil -- 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
