Bug 1826251
| Summary: | remove MD metadata 0.90 based tests from util-linux CI | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Karel Zak <kzak> |
| Component: | util-linux | Assignee: | Karel Zak <kzak> |
| Status: | CLOSED ERRATA | QA Contact: | Radka Brychtova <rskvaril> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.3 | CC: | bgoncalv, dledford, dmilburn, ncroxon, xni |
| Target Milestone: | rc | Keywords: | Reopened |
| Target Release: | 8.3 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | util-linux-2.32.1-23.el8 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-11-04 02:06:13 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: | |||
|
Description
Karel Zak
2020-04-21 10:22:41 UTC
To answer your question: It seems mdadm on RHEL-8 does not support metadata 0.90 anymore. Is it expected?
We have NOT drop support for metadata 0.90.
Can you do an "rpm -qa |grep mdadm". And share the output?
# mdadm --create /dev/md8 --metadata=0.90 --chunk=64 --level=0 --raid-devices=2 /dev/nvme2n1 /dev/nvme3n1
mdadm: array /dev/md8 started.
[root@localhost ncroxon]# mdadm -D /dev/md8
/dev/md8:
Version : 0.90
Creation Time : Tue Apr 21 09:26:44 2020
Raid Level : raid0
Array Size : 1000215040 (953.88 GiB 1024.22 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 8
Persistence : Superblock is persistent
Update Time : Tue Apr 21 09:26:44 2020
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Chunk Size : 64K
Consistency Policy : none
UUID : 69798448:6a8475f6:bfe78010:bc810f04 (local to host localhost.localdomain)
Events : 0.1
Number Major Minor RaidDevice State
0 259 10 0 active sync /dev/nvme2n1
1 259 9 1 active sync /dev/nvme3n1
[root@localhost ncroxon]#
# rpm -qa|grep mdadm
mdadm-4.1-10.el8.x86_64
I stand correct. I need to check with my co-worker on the following patch: https://www.spinics.net/lists/raid/msg63440.html -Nigel I can confirm we have picked up the two patches which print the message you encountered. -Create-add-support-for-RAID0-layouts.patch Since Linux 5.4 a layout is needed for RAID0 arrays with varying device sizes. This patch makes the layout of an array visible (via --examine) and sets the layout on newly created arrays. -Assemble-add-support-for-RAID0-layouts.patch If you have a RAID0 array with varying sized devices on a kernel before 5.4, you cannot assembling it on 5.4 or later without explicitly setting the layout. Hi Karel I looked the codes. The answer is 0.9 metadata doesn't support raid0 from mdadm-4.1-12 any more. So you can remove the case now. Close this bug. Thanks Xiao My comments are not accurate. It can't create new raid0 from mdadm-4.1-12. But if you have created raid0, it can still assemble it. But it needs to specify default_layout=1 when modprobe raid0 Thanks for your feedback. I'll reopen it for util-linux to remove the test from CI tests. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (util-linux bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4575 |