RAID0 MD VD still exists after surprise removing one of the component drives

This document (000021155) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 15 SP5

Situation

The device node for RAID0 MD VD still exists after surprise removing one of the component drives.
The expectation is that after surprise removing one of the component drives, the /dev/md0 node should get deleted.

Steps to reproduce the problem:

1. Setup with NVMe drives and verify the drives are discovered successfully.
2. Create a MD Virtual Disk:
# mdadm --create /dev/md0 --level=0 --raid-devices=2 /dev/nvme2n1p1 /dev/nvme3n1p1
3. Note the MD VD status:
# mdadm -D /dev/md0
4. Surprise remove one of the drives.
5. Verify if /dev/md0 exists and note it's state:
# mdadm -D /dev/md0
or 
# cat /proc/mdstat

Expected result: /dev/md0 should not exist after step 4.

Resolution

The kernel update released August 14, 2023 ( -5.14.21-150500.55.19.1 ) includes the patch to resolve the problem.

Cause

The MD_BROKEN flag is not set for RAID0 MD VDs.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.