Re: [REGRESSION] 6.7.1: md: raid5 hang and unresponsive system; successfully bisected

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2/21/24 6:50 AM, Mateusz Kusiak wrote:
On 21.02.2024 00:15, junxiao.bi@xxxxxxxxxx wrote:

The thing is we can't reproduce this issue at all. If you can generate a vmcore when the hung happened, then we can review which processes are stuck.

Hi,
don't know if that be any of help, but I run below scenario with SATA and NVMe drives. For me, the issue is reproducible on NVMe drives only.

Scenario:
1. Create R5D3 with native metadata
    # mdadm -CR /dev/md/vol -l5 -n3 /dev/nvme[0-2]n1 --assume-clean
2. Create FS on the array
    # mkfs.ext4 /dev/md/vol -F
3. Remove single member drive via "--incremental --fail"
    # mdadm -If nvme0n1

The result is almost instant.

This is not the same issue that Dan reported, it looks like another regression that Yu Kuai fixed , can you please try this patch?

https://lore.kernel.org/lkml/95f2e08e-2daf-e298-e696-42ebfa7b9bbf@xxxxxxxxxxxxxxx/

Thanks,

Junxiao.


Thanks,
Mateusz




[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux