raid测试中出现D状态

【标题描述】能够简要描述问题：说明什么场景下，做了什么操作，出现什么问题（尽量使用正向表达方式）
raid测试中出现D状态
。

【环境信息】
虚拟机
eulerversion=EulerOS_Server_V200R010C00B550_x86_64
compiletime=2021-12-20-12-12-22
kernelversion=4.18.0-147.5.2.5.h777

【问题复现步骤】
raid 测试用例中，mdam –a 和 mdadm –S 顺序执行后，立即移除raid依赖的磁盘。
mdadm -a 会触发一个异步线程进行同步/恢复。 而 mdadm -S 执行之后，立刻拔掉了raid依赖的磁盘
当线程执行成功后，会上报一个udev事件触发查询动作，而此时raid设备的磁盘已经被移除，导致IO无法返回，从而出现了D状态
出现概率较小
【预期结果】
不会出现raid阵列残留和D状态进程
【实际结果】
raid阵列残留和有mdadm的D状态进程
【附件信息】
Dec 31 02:13:39 localhost kernel: [17818.591091] INFO: task mdadm:242358 blocked for more than 120 seconds.
Dec 31 02:13:39 localhost kernel: [17818.592632]       Tainted: G           O     --------- -  - 4.18.0-147.5.1.6.h638.eulerosv2r9.x86_64 #1
Dec 31 02:13:39 localhost kernel: [17818.594760] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec 31 02:13:39 localhost kernel: [17818.596531] mdadm           D    0 242358 242347 0x00000180
Dec 31 02:13:39 localhost kernel: [17818.596534] Call Trace:
Dec 31 02:13:39 localhost kernel: [17818.596542]  ? __schedule+0x2fc/0x930
Dec 31 02:13:39 localhost kernel: [17818.596544]  ? schedule+0x28/0x70
Dec 31 02:13:39 localhost kernel: [17818.596546]  ? io_schedule+0x12/0x40
Dec 31 02:13:39 localhost kernel: [17818.596550]  ? do_read_cache_page+0x4c7/0x750
Dec 31 02:13:39 localhost kernel: [17818.596553]  ? blkdev_writepages+0x10/0x10
Dec 31 02:13:39 localhost kernel: [17818.596555]  ? page_cache_tree_insert+0xe0/0xe0
Dec 31 02:13:39 localhost kernel: [17818.596559]  ? read_dev_sector+0x28/0xc0
Dec 31 02:13:39 localhost kernel: [17818.596561]  ? read_lba+0x126/0x210
Dec 31 02:13:39 localhost kernel: [17818.596563]  ? kmem_cache_alloc_trace+0x1a6/0x1c0
Dec 31 02:13:39 localhost kernel: [17818.596565]  ? efi_partition+0x137/0x760
Dec 31 02:13:39 localhost kernel: [17818.596567]  ? vsnprintf+0x410/0x4d0
Dec 31 02:13:39 localhost kernel: [17818.596568]  ? vsnprintf+0xfe/0x4d0
Dec 31 02:13:39 localhost kernel: [17818.596569]  ? snprintf+0x45/0x70
Dec 31 02:13:39 localhost kernel: [17818.596571]  ? is_gpt_valid.part.0+0x400/0x400
Dec 31 02:13:39 localhost kernel: [17818.596572]  ? check_partition+0x13a/0x240
Dec 31 02:13:39 localhost kernel: [17818.596573]  ? check_partition+0x13a/0x240
Dec 31 02:13:39 localhost kernel: [17818.596574]  ? rescan_partitions+0x7f/0x330
Dec 31 02:13:39 localhost kernel: [17818.596576]  ? bdev_disk_changed+0x8c/0xa0
Dec 31 02:13:39 localhost kernel: [17818.596578]  ? __blkdev_get+0x37d/0x590
Dec 31 02:13:39 localhost kernel: [17818.596579]  ? blkdev_get+0x149/0x3a0
Dec 31 02:13:39 localhost kernel: [17818.596582]  ? selinux_file_open+0x9d/0xf0
Dec 31 02:13:39 localhost kernel: [17818.596584]  ? blkdev_get_by_dev+0x40/0x40
Dec 31 02:13:39 localhost kernel: [17818.596587]  ? do_dentry_open+0x1d5/0x370
Dec 31 02:13:39 localhost kernel: [17818.596589]  ? path_openat+0x557/0x1730
Dec 31 02:13:39 localhost kernel: [17818.596591]  ? mem_cgroup_commit_charge+0x7f/0x4e0
Dec 31 02:13:39 localhost kernel: [17818.596593]  ? mem_cgroup_try_charge+0x86/0x180
Dec 31 02:13:39 localhost kernel: [17818.596594]  ? do_filp_open+0x9b/0x110
Dec 31 02:13:39 localhost kernel: [17818.596597]  ? page_counter_try_charge+0x58/0xc0
Dec 31 02:13:39 localhost kernel: [17818.596600]  ? files_cgroup_alloc_fd+0x38/0x60
Dec 31 02:13:39 localhost kernel: [17818.596602]  ? __alloc_fd+0xd4/0x250
Dec 31 02:13:39 localhost kernel: [17818.596604]  ? do_sys_open+0x1bd/0x250
Dec 31 02:13:39 localhost kernel: [17818.596606]  ? do_sys_open+0x1bd/0x250
Dec 31 02:13:39 localhost kernel: [17818.596609]  ? do_syscall_64+0x5b/0x1b0
Dec 31 02:13:39 localhost kernel: [17818.596611]  ? entry_SYSCALL_64_after_hwframe+0x65/0xca
Dec 31 02:13:39 localhost kernel: [17818.596614] INFO: task blkid:242417 blocked for m
详细日志见附件

GVP openEuler/kernel

Content Risk Flag

Comments (2)

GVPopenEuler/kernel

Content Risk Flag