diff options
author | Kinga Tanska <kinga.tanska@intel.com> | 2019-12-10 12:21:21 +0100 |
---|---|---|
committer | Jes Sorensen <jsorensen@fb.com> | 2020-01-16 19:48:13 +0100 |
commit | 1a87493014050e3bd94000cd36122c3cadf21270 (patch) | |
tree | 788fafa8b04baf930883c1b2645588d2a0414606 /mdopen.c | |
parent | Respect $(CROSS_COMPILE) when $(CC) is the default (diff) | |
download | mdadm-1a87493014050e3bd94000cd36122c3cadf21270.tar.xz mdadm-1a87493014050e3bd94000cd36122c3cadf21270.zip |
Change warning message
In commit 039b7225e6 ("md: allow creation of mdNNN arrays via
md_mod/parameters/new_array") support for name like mdNNN
was added. Special warning, when kernel is unable to handle
request, was added in commit 7105228e19
("mdadm/mdopen: create new function create_named_array for
writing to new_array"), but it was not adequate enough,
because in this situation mdadm tries to do it in old way.
This commit changes warning to be more relevant when
creating RAID container with "/dev/mdNNN" name and mdadm
back to old approach.
Signed-off-by: Kinga Tanska <kinga.tanska@intel.com>
Signed-off-by: Jes Sorensen <jsorensen@fb.com>
Diffstat (limited to 'mdopen.c')
-rw-r--r-- | mdopen.c | 3 |
1 files changed, 2 insertions, 1 deletions
@@ -120,7 +120,8 @@ int create_named_array(char *devnm) close(fd); } if (fd < 0 || n != (int)strlen(devnm)) { - pr_err("Fail create %s when using %s\n", devnm, new_array_file); + pr_err("Fail to create %s when using %s, fallback to creation via node\n", + devnm, new_array_file); return 0; } |