This repository has been archived by the owner on Oct 12, 2020. It is now read-only.
Manage: in clustered environments, when raid1 is recovering , add new disk failed? #37
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It supports to specify the argument of "--raidtype" to run the different raid level cases. Details refer to the do_help() usage. For example: ./test --raidtype=raid1 could execute all the raid1 test cases under tests/. Signed-off-by: Zhilong Liu <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
If test mode has set as '--dev=disk', then users can specify
the argument of "--disks" to test a bunch of physical devices.
For example: ./test --dev=disk --disks=/dev/sda{2..15}
could execute all test cases on physical devices.
Currently, the --dev=disk mode would confilct with testdev()
in current test cases, thus ignore testing testdev() if has
set --dev=disk mode.
Signed-off-by: Zhilong Liu <[email protected]>
Signed-off-by: Jes Sorensen <[email protected]>
If symlink (e.g. /dev/md/raid) is passed as a parameter to mdadm --wait, it fails as it's not able to find a corresponding entry in /proc/mdstat output. Get parameter file major:minor and look for block device name in sysfs. This commit is partial revert of commit 9e04ac1 ("mdadm/util: unify stat checking blkdev into function"). Signed-off-by: Tomasz Majchrzak <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
Currently if metadata requires more then 1M, data offset will be rounded down to closest MB. This is not correct, since less then required space is reserved. Always round data offset up to multiple of 1M. Signed-off-by: Pawel Baldysiak <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
Currently, --add-journal can be only used to recreate broken journal for arrays with journal since creation. As the kernel code getting more mature, this constraint is no longer necessary. This patch allows --add-journal to add journal to array without journal. Signed-off-by: Song Liu <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
For cluster scenario, add device is different with native raid. When a node issues adds a device, then the node will broadcast a message with UUID to other nodes in the cluster. If receiving node can find the device with the specific UUID, it must confirm the device, otherwise reports it is missing. Signed-off-by: Guoqing Jiang <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
The check for inactive array is incorrect as it compares it against active array. Introduce a new function md_is_array_active so the check is consistent across the code. As the output contains list of disks in the array include this information in sysfs read. Signed-off-by: Mariusz Tkaczyk <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
When RAID10 loses 2 disks and it is still operational, it cannot be rebuilt. The rebuild process starts for the first disk and completes, however completion is not recorded in metadata. There is an assumption that rebuild completion corresponds to transition from degraded to normal state. It's not the case for 2-disk RAID10 as it's still degraded after rebuild to first disk completes. Check if disk rebuild flag is set in the second map and clear it. So far it has been checked only in the first map (where it was not set). The flag in the second map has not been cleared but rebuild completion dropped second map so the problem was not visible. If rebuild completion is notified and array still has failed disks and is in degraded state, check first if rebuild position is really unset (the same check as for array in normal state). If so, mark migration as done but don't change array state (it should remain degraded). Update failed disk number. On rebuild start don't clear the rebuild flag in the destination map for all the drives because failed state is lost for one of them. Just do a copy of a map and clear the flag in the destination map for the disk that goes into rebuild. Similarily preserve the rebuild flag in the map during disk removal. If the disk is missing on array start and migration has been in progress, don't just cancel it. Check first if maybe one of the disks was not under rebuild (rebuild flag present both in source and destination map). If so, rebuild was running despite of failed disk so there is no need to cancel migration. Signed-off-by: Tomasz Majchrzak <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
Add "\n" to the end of error messages which don't already have one. Also spell "opened" correctly. Signed-off-by: NeilBrown <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
${DEVLINKS}
is not valid udev syntax, and is passed through uninterpreted.
$env{DEVLINKS}
or
%e{DEVLINKS}
is correct.
Signed-off-by: NeilBrown <[email protected]>
Signed-off-by: Jes Sorensen <[email protected]>
If no bitmap is present, then the test if (__le32_to_cpu(bsb->nodes) > 1) accesses uninitialised memory. So move that test inside a test for a bitmap being present. Signed-off-by: NeilBrown <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
mdadm uses smaller exit codes like 0,1,2,3,4. Using ERANGE is inconsistent and not helpful. So change it to a more consistent number. Signed-off-by: NeilBrown <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
GET_MISMATCH option doesn't exist for containers so sysfs_read fails if this information is requested. Set options according to the device using information from /proc/mdstat. Signed-off-by: Mariusz Tkaczyk <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
Spare migration doesn't work for external metadata. mdadm skips a container with spare device because it is inactive. It used to work because GET_ARRAY_INFO ioctl returned valid structure for a container and mdadm treated such response as active container. Current implementation checks it in sysfs where container is shown as inactive. Adapt sysfs implementation to work the same way as ioctl. Signed-off-by: Mariusz Tkaczyk <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
Containers used to be handled as active arrays because GET_ARRAY_INFO ioctl returns valid structure for them. As containers appear as inactive in sysfs, the output for detail command has changed. Stop relying on inactive state for containers. Make the output look the same as in mdadm 4.0. Signed-off-by: Mariusz Tkaczyk <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
To avoid rpmbuild error. Signed-off-by: Song Liu <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
Summary: In Incremental.c:count_active(), max_events is tracked to show to which devices are up to date. If a device has events==max_events+1, getinfo_super() is called to reload the superblock from this device. getinfo_super1() blindly set journal_clean to 0, which is wrong. This patch fixes this by tracking max_journal_events for all the disks. After scanning all disks, journal_clean is set if max_journal_events >= max_events-1. Signed-off-by: Song Liu <[email protected]> Reviewed-by: NeilBrown <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
--examine-bitmap: the bitmap_file_open() shouldn't omit the regular file descriptor when the bitmap is external mode. Such as: ./mdadm -X /mnt/3 This commit is partial revert of commit 0a6bff0 (mdadm/util: unify fstat checking blkdev into function) Signed-off-by: Zhilong Liu <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
it would complain "too many arguments" when array[] has few members, it's proper to check whether or not array[0] is null. Reported-by: Xiao Ni <[email protected]> Signed-off-by: Zhilong Liu <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
It's time to get rid of the tests/testdev due to it has covered by testdev() in new 'test'. Signed-off-by: Zhilong Liu <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
The tests/check can be removed due to check() in new 'test' has covered various checking. Signed-off-by: Zhilong Liu <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
This is a test case for testing --readonly and --readwrite feature, it covers common metadata versions and raid levels. Signed-off-by: Zhilong Liu <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
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 <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
Make devid2kname() and devid2devnm() consistent in their APIs Signed-off-by: Jes Sorensen <[email protected]>
Be consistent and use the correct type. Signed-off-by: Jes Sorensen <[email protected]>
Use the correct type for rdev Signed-off-by: Jes Sorensen <[email protected]>
Lets not make things uglier than they need to be. Signed-off-by: Jes Sorensen <[email protected]>
Signed-off-by: Xiao Ni <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
If array is stopped during reshape and assembled again straight away, reshape process in a background might still be running. systemd doesn't start a new service if one already exists. If there is a race, previous process might terminate and new one is not created. Reshape doesn't continue after assemble. Tell systemd to restart the service rather than just start it. It will assure previous service is stopped first. If it's not running, stopping has no effect and only new process is started. Signed-off-by: Tomasz Majchrzak <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
Add disk controller domain for nvme and vmd devices to prevent moving spares between different domains. Signed-off-by: Mariusz Tkaczyk <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
Adding support for Tebibytes enables display size of volumes in Tebibytes and Terabytes when they are bigger than 2048 GiB (or GB). Signed-off-by: Kinga Tanska <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
Imsm tracks as "working_disk" each visible drive. Assemble routine expects that the value will return count of active member drives recorded in metadata. As a side effect "--no-degraded" doesn't work correctly for imsm. Align this field to others. Added check, if the option --no-degraded is called with --scan. Signed-off-by: Blazej Kucman <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
When growing a raid0 device, if the new component disk size is not big enough, the grow operation may fail due to lack of backup space. The minimum backup space should be larger than: LCM(old, new) * chunk-size * 2 where LCM() is the least common multiple of the old and new count of component disks, and "* 2" comes from the fact that mdadm refuses to use more than half of a spare device for backup space. There are users reporting such failure when they grew a raid0 array with small component disk. Neil Brown points out this is not a bug and how the failure comes. This patch adds note information into mdadm(8) man page in the Notes part of GROW MODE section to explain the minimum size requirement of new component disk size or external backup size. Reviewed-by: Petr Vorel <[email protected]> Cc: NeilBrown <[email protected]> Cc: Jes Sorensen <[email protected]> Cc: Paul Menzel <[email protected]> Cc: Wols Lists <[email protected]> Cc: Nix <[email protected]> Signed-off-by: Coly Li <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
The whitespace between Environment= and the true value causes confusion. To avoid confusing other people in future, remove the whitespace to keep it a simple, unambiguous syntax Signed-off-by: Xiao Ni <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
After patch b618016 ("imsm: save current_vol number") current_vol for imsm is not set and kill_subarray() cannot determine which volume has to be deleted. Volume has to be passed as "subarray_id". The parameter affects only IMSM metadata. Signed-off-by: Blazej Kucman <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
Functionalities --dump and --restore are not supported. Remove dead code from imsm. Signed-off-by: Blazej Kucman <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
Check if given size of member drive is not less than 1 MibiByte. Signed-off-by: Blazej Kucman <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
Signed-off-by: Lidong Zhong <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
Also present its value in --examine and --examine --export. Signed-off-by: Artur Paszkiewicz <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
Show the index of the subarray as 'Subarray' and the value of the my_vol_raid_dev_num field as 'Volume ID'. Signed-off-by: Artur Paszkiewicz <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
When adding a device to a container mdadm has to close its file descriptor before sysfs_add_disk(). This generates change event. There is race possibility because metadata is already written and other -I process can place drive differently. As a result device can be added to two containers simultaneously. From IMSM perspective there is no need to react for change event. IMSM doesn't support stacked devices. Signed-off-by: Mariusz Tkaczyk <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
When running mdadm monitor with scan mode, only one autorebuild process
is allowed. check_one_sharer() checks duplicated process by following
steps,
1) Read autorebuild.pid file,
- if file does not exist, no duplicated process, go to 3).
- if file exists, continue to next step.
2) Read pid number from autorebuild.pid file, then check procfs pid
directory /proc/<PID>,
- if the directory does not exist, no duplicated process, go to 3)
- if the directory exists, print error message for duplicated process
and exit this mdadm.
3) Write current pid into autorebuild.pid file, continue to monitor in
scan mode.
The problem for the above step 2) is, if after system reboots and
another different process happens to have exact same pid number which
autorebuild.pid file records, check_one_sharer() will treat it as a
duplicated mdadm process and returns error with message "Only one
autorebuild process allowed in scan mode, aborting".
This patch tries to fix the above same-pid-but-different-process issue
by one more step to check the process command name,
1) Read autorebuild.pid file
- if file does not exist, no duplicated process, go to 4).
- if file exists, continue to next step.
2) Read pid number from autorebuild.pid file, then check procfs file
comm with the specific pid directory /proc/<PID>/comm
- if the file does not exit, it means the directory /proc/<PID> does
not exist, go to 4)
- if the file exits, continue next step
3) Read process command name from /proc/<PIC>/comm, compare the command
name with "mdadm" process name,
- if not equal, no duplicated process, goto 4)
- if strings are equal, print error message for duplicated process
and exit this mdadm.
4) Write current pid into autorebuild.pid file, continue to monitor in
scan mode.
Now check_one_sharer() returns error for duplicated process only when
the recorded pid from autorebuild.pid exists, and the process has exact
same command name as "mdadm".
Reported-by: Shinkichi Yamazaki <[email protected]>
Signed-off-by: Coly Li <[email protected]>
Signed-off-by: Jes Sorensen <[email protected]>
On the node with /proc/mdstat is
Personalities : [raid1]
md0 : active raid1 sdb[4] sdc[3] sdd[2]
1046528 blocks super 1.2 [3/2] [UU_]
recover=REMOTE
bitmap: 1/1 pages [4KB], 65536KB chunk
Let's change the 'State' of 'mdadm -Q -D' accordingly
State : clean, degraded
With this patch, it will be
State : clean, degraded, recovering (REMOTE)
Signed-off-by: Lidong Zhong <[email protected]>
Acked-by: Guoqing Jiang <[email protected]>
Signed-off-by: Jes Sorensen <[email protected]>
New drive in container always appears as spare. Manager is able to handle that, and queues appropriative update to monitor. No update from mdadm side has to be processed, just insert the drive and ping the mdmon. Metadata has to be written if no mdmon is running (case for Raid0 or container without arrays). If bare drive is added very early on startup (by custom bare rule), there is possiblity that mdmon was not restarted after switch root. Old one is not able to handle new drive. New one fails because there is drive without metadata in container and metadata cannot be loaded. To prevent this, write spare metadata before adding device to container. Mdmon will overwrite it (same case as spare migration, if drive appears it writes the most recent metadata). Metadata has to be written only on new drive before sysfs_add_disk(), don't race with mdmon if running. Signed-off-by: Tkaczyk Mariusz <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
…ption
When mdadm tries to assemble one working device and one zeroed-out device,
it failed but print successful message because there is --uuid option.
Following script always reproduce it.
dd if=/dev/zero of=/dev/ram0 oflag=direct
dd if=/dev/zero of=/dev/ram1 oflag=direct
./mdadm -C /dev/md111 -e 1.2 --uuid="12345678:12345678:12345678:12345678" \
-l1 -n2 /dev/ram0 /dev/ram1
./mdadm -S /dev/md111
dd if=/dev/zero of=/dev/ram1 oflag=direct
./mdadm -A /dev/md111 --uuid="12345678:12345678:12345678:12345678" \
/dev/ram0 /dev/ram1
Following is message from mdadm.
mdadm: No super block found on /dev/ram1 (Expected magic a92b4efc, got 00000000)
mdadm: no RAID superblock on /dev/ram1
mdadm: /dev/md111 assembled from 1 drive - need all 2 to start it (use --run to insist).
The mdadm say that it assembled but mdadm does not create /dev/md111.
The message is wrong.
After applying this patch, mdadm reports error correctly as following.
mdadm: No super block found on /dev/ram1 (Expected magic a92b4efc, got 00000000)
mdadm: no RAID superblock on /dev/ram1
mdadm: /dev/ram1 has no superblock - assembly aborted
Signed-off-by: Gioh Kim <[email protected]>
Signed-off-by: Jes Sorensen <[email protected]>
Clean up the typo which leads to wrong understanding. Signed-off-by: Nigel Croxon <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
If the array is dirty handler will set resync_start to 0 to inform kernel that resync is needed. RWH affects only raid456 module, for other levels array will be started even array is degraded and resync cannot be performed. Force is really meaningful for raid456. If array is degraded and resync is requested, kernel will reject an attempt to start the array. To respect force, it has to be marked as clean (this will be done for each array without PPL) and remove the resync request (only for raid 456). Data corruption may occur so proper warning is added. Signed-off-by: Mariusz Tkaczyk <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
Currently mdcheck (when called with `--duration`) logs only the
beginning of the check, the pausing and the continuation but not the
completion.
So, log the completion, too, so that it can be determined how long the
raid check took.
2020-05-08T18:00:02+02:00 deadpool root: mdcheck start checking /dev/md0
2020-05-08T18:00:02+02:00 deadpool root: mdcheck start checking /dev/md1
2020-05-09T15:32:04+02:00 deadpool root: mdcheck finished checking /dev/md1
2020-05-09T17:38:04+02:00 deadpool root: mdcheck finished checking /dev/md0
Cc: [email protected]
Signed-off-by: Paul Menzel <[email protected]>
Signed-off-by: Jes Sorensen <[email protected]>
Add optional EXTRAVERSION parameter to Makefile and allow to mark version by user friendly label. It might be useful when creating custom spins of mdadm, or labeling some instance in between major releases. Signed-off-by: Tkaczyk Mariusz <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
Currently, 'make raid6check' is build broken since commit b068159 ("mdadm: load default sysfs attributes after assemblation"). /usr/bin/ld: sysfs.o: in function `sysfsline': sysfs.c:(.text+0x2707): undefined reference to `parse_uuid' /usr/bin/ld: sysfs.c:(.text+0x271a): undefined reference to `uuid_zero' /usr/bin/ld: sysfs.c:(.text+0x2721): undefined reference to `uuid_zero' Apparently, the compile of mdadm or raid6check are coupled with uuid functions inside util.c. However, we can't just add util.o to CHECK_OBJS which raid6check is needed, because it caused other worse problems. So, let's introduce a uuid.c file which is indenpended file to fix the problem, all the contents are splitted from util.c. Signed-off-by: Guoqing Jiang <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
We have to include the \0 character in the length when copying a string with strncpy() for which length was found with strlen(). Otherwise the destination will not get null terminated - except that we explicitly zeroed it out earlier. This quiets down the compiler's warnings. Signed-off-by: Jes Sorensen <[email protected]>
Got below error when run "make everything".
restripe.c: In function ‘test_stripes’:
restripe.c:870:4: error: ignoring return value of ‘read’, declared with attribute warn_unused_result [-Werror=unused-result]
read(source[i], stripes[i], chunk_size);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Fix it by check the return value of ‘read’, and free memory
in the failure case.
And check the return value of lseek as well per Jes's comment.
Signed-off-by: Guoqing Jiang <[email protected]>
Signed-off-by: Jes Sorensen <[email protected]>
Manual assembly with existing link caused overwriting this link. Add checking link and block this situation. Signed-off-by: Kinga Tanska <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
For 1.x metadata, when the user requested creation of an array on component devices that were too small even to hold the superblock, an undetected integer wraparound (underflow) resulted in an enormous computed size which resulted in various follow-on errors such as floating-point exception. This patch detects this condition, prints a reasonable diagnostic message, and refuses to continue. Signed-off-by: David Favro <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
All URLs in the source are available over HTTPS, so convert all URLs to
HTTPS with the command below.
git grep -l 'http://' | xargs sed -i 's,http://,https://,g'
Revert the changes to announcement files `ANNOUNCE-*` as requested by
the maintainer.
Cc: [email protected]
Signed-off-by: Paul Menzel <[email protected]>
Signed-off-by: Jes Sorensen <[email protected]>
The old design page is gone, so update to the current overview page. Signed-off-by: Jes Sorensen <[email protected]>
If we start reshaping on md which shares sub-devices with another resyncing md, it may be forced to wait for others to complete. mdadm occupies the md's fd during this time, which causes the md can not be stopped and the filesystem can not be mounted on the md. We can close md's fd earlier to solve this problem. Reproducible Steps: 1. create two partitions on sda, sdb, sdc, sdd 2. create raid1 with sda1, sdb1 mdadm -C /dev/md1 --assume-clean -l1 -n2 /dev/sda1 /dev/sdb1 3. create raid5 with sda2, sdb2, sdc2 mdadm -C /dev/md2 --assume-clean -l5 -n3 /dev/sda2 /dev/sdb2 /dev/sdc2 4. start resync at md1 echo repair > /sys/block/md1/md/sync_action 5. reshape raid5 to raid6 mdadm -a /dev/md2 /dev/sdd2 mdadm --grow /dev/md2 -n4 -l6 --backup-file=/root/md2-backup Now mdadm is occupying the fd of md2, causing md2 unable to be stopped 6.Try to stop md2, an error message shows mdadm -S /dev/md2 mdadm: Cannot get exclusive access to /dev/md3:Perhaps a running process, mounted filesystem or active volume group? Reviewed-by: Alex Wu <[email protected]> Reviewed-by: BingJing Chang <[email protected]> Reviewed-by: Danny Shih <[email protected]> Signed-off-by: ChangSyun Peng <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
Now it allows updating cluster nodes without specify --nodes. It can write superblock with zero nodes. It can break the current cluster. Add this check to avoid this problem. v2: It needs check c.update first to avoid NULL pointer reference v3: Wol points the typo error Signed-off-by: Xiao Ni <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
Documentation/md.txt was renamed to Documentation/admin-guide/md.rst in linux commit 9d85025b0418163fae079c9ba8f8445212de8568 (Oct 26, 2016). Signed-off-by: Winston Weinert <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
IMSM also supports it. Signed-off-by: Mariusz Tkaczyk <[email protected]> Signed-off-by: Jes Sorensen <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I use the kernel is Linux version4.14.78, In clustered environments, when raid1 is recovering(not resyncing),I try to add new disk with the command mdadm --manage /dev/md125 -a /dev/sdd, in this case, userspace report the error,is it a bug ?