Bug 2158730

Summary: Cannot assemble DDF array with 6.2 kernel
Product: [Fedora] Fedora Reporter: Vojtech Trefny <vtrefny>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rawhideCC: acaringi, adscvr, agk, airlied, alciregi, bskeggs, dledford, hdegoede, hpa, jarodwilson, jes.sorensen, jglisse, jonathan, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, ptalbert, steved, xni
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-01-26 13:59:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2158574, 2163711    

Description Vojtech Trefny 2023-01-06 11:15:00 UTC
Version-Release number of selected component (if applicable):

$ mdadm --version
mdadm - v4.2 - 2021-12-30

$ uname -r
6.2.0-0.rc1.20221230gitbff687b3dad6.15.fc38.x86_64

Steps to Reproduce:

$ sudo mdadm --create /dev/md/test --run --level=container --metadata=ddf --raid-devices=2 /dev/sdb /dev/sdc -v
mdadm: size set to 479232K
mdadm: ADD_NEW_DISK for /dev/sdb failed: Invalid argument

from journal:
Jan 06 12:06:25 fedora kernel: md: could not open device unknown-block(8,16).

Additional info:

We hit this issue in libblockdev[1] test suite and this is on a system without real BIOS RAID support so it is possible this a cause behind this issue, but it works on older versions of Fedora.

[1] https://github.com/storaged-project/libblockdev

Comment 1 Vojtech Trefny 2023-01-23 09:26:22 UTC
I can both create and activate the DDF array on Fedora 37 with the same version of mdadm so I am moving this to kernel. I've also change the title since the DDF container can be created on F37 but cannot be activated on F38

# mdadm --assemble --scan
mdadm: failed to add /dev/sdc to /dev/md/ddf: Invalid argument
mdadm: failed to add /dev/sdb to /dev/md/ddf: Invalid argument
mdadm: Container /dev/md/ddf has been assembled with 0 drives (out of 2)
mdadm: timeout waiting for /dev/md/ddf

from journal:
Jan 23 09:15:14 fedora kernel: md: could not open device unknown-block(8,16).
Jan 23 09:15:14 fedora kernel: md: could not open device unknown-block(8,32).
Jan 23 09:15:14 fedora kernel: md: md127 stopped.
Jan 23 09:15:14 fedora kernel: block device autoloading is deprecated and will be removed.


I am also raising the severity because it is blocking the F38 change[1] to switch from dmraid to mdadm for BIOS RAID support.


[1] https://fedoraproject.org/wiki/Changes/UseMdadmForBIOSRAIDInAnaconda

Comment 2 Vojtech Trefny 2023-01-26 13:59:54 UTC
This now works with the latest kernel 6.2.0-0.rc5.20230125git948ef7bb70c4.40.fc38.x86_64 in today Fedora.