Creating an array by opening a block-device with major number of 9 will transparently load the md module if needed. Creating an array by opening /sys/module/md_mod/parameters/new_array and writing to it won't, it will just fail if md_mod isn't loaded. So when opening that file fails with ENOENT, run "modprobe md_mod" and try again. This fixes a bug whereby if you have "CREATE names=yes" in mdadm.conf, and the md modules isn't loaded, then creating or assembling an array will not honor the "names=yes" configuration. Signed-off-by: NeilBrown <neilb@xxxxxxxx> --- mdopen.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/mdopen.c b/mdopen.c index 3c0052f2db23..dcdc6f23e6c1 100644 --- a/mdopen.c +++ b/mdopen.c @@ -312,6 +312,10 @@ int create_mddev(char *dev, char *name, int autof, int trustworthy, if (block_udev) udev_block(devnm); fd = open("/sys/module/md_mod/parameters/new_array", O_WRONLY); + if (fd < 0 && errno == ENOENT) { + system("modprobe md_mod"); + fd = open("/sys/module/md_mod/parameters/new_array", O_WRONLY); + } if (fd >= 0) { n = write(fd, devnm, strlen(devnm)); close(fd); -- 2.14.0.rc0.dirty
Attachment:
signature.asc
Description: PGP signature