diff options
| author | Guoqing Jiang <jgq516@gmail.com> | 2019-07-24 11:09:20 +0200 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-10-05 12:27:47 +0200 |
| commit | 6b544c54638b36610c5154ebf8243124f10f6aa5 (patch) | |
| tree | 367d6a0aa50f856f841c96944aa30b8cad4d5cd3 /include/uapi/linux/msg.h | |
| parent | 6809adb82cea49a131ee6de36c45950b11821dc5 (diff) | |
md: don't set In_sync if array is frozen
[ Upstream commit 062f5b2ae12a153644c765e7ba3b0f825427be1d ]
When a disk is added to array, the following path is called in mdadm.
Manage_subdevs -> sysfs_freeze_array
-> Manage_add
-> sysfs_set_str(&info, NULL, "sync_action","idle")
Then from kernel side, Manage_add invokes the path (add_new_disk ->
validate_super = super_1_validate) to set In_sync flag.
Since In_sync means "device is in_sync with rest of array", and the new
added disk need to resync thread to help the synchronization of data.
And md_reap_sync_thread would call spare_active to set In_sync for the
new added disk finally. So don't set In_sync if array is in frozen.
Signed-off-by: Guoqing Jiang <guoqing.jiang@cloud.ionos.com>
Signed-off-by: Song Liu <songliubraving@fb.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'include/uapi/linux/msg.h')
0 files changed, 0 insertions, 0 deletions
