Bug 2149307
| Summary: | mdadm: Couldn't open /dev/vda3 for write - not zeroing | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Jan Stodola <jstodola> | ||||||||
| Component: | mdadm | Assignee: | XiaoNi <xni> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fine Fan <ffan> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 8.8 | CC: | bugproxy, ffan, jikortus, ncroxon, vtrefny, xni | ||||||||
| Target Milestone: | rc | Keywords: | Regression, Triaged | ||||||||
| Target Release: | --- | ||||||||||
| Hardware: | All | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | mdadm-4.2-7.el8 | Doc Type: | If docs needed, set a value | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2023-05-16 09:09:23 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: | 2129764, 2144443 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Jan Stodola
2022-11-29 14:33:39 UTC
Hi Jan Could you have a try with https://people.redhat.com/xni/mdadm-4.2-7.el8.x86_64.rpm Thanks Xiao Created new installation images from compose RHEL-8.8.0-20221204.2 + mdadm-4.2-7.el8.x86_64.rpm, but the problem persists. Hi Jan Thanks for the check. There are some packages that have been updated. Could you have a try with RHEL-8.8.0-20221204.2 + mdadm-4.2-5.el8.x86_64.rpm (http://download.eng.bos.redhat.com/brewroot/packages/mdadm/4.2/5.el8/x86_64/mdadm-4.2-5.el8.x86_64.rpm) If it can't be reproduced, we can make sure it's a regression problem which is introduced by mdadm-4.2-6
The messages is printed by those codes
fd = open(dev, O_RDWR|(noexcl ? 0 : O_EXCL));
if (fd < 0) {
if (verbose >= 0)
pr_err("Couldn't open %s for write - not zeroing\n",
dev);
return 2;
}
So not sure why it can't open /dev/vda3 but it can open /dev/vda2
Hi Jan Could you give your ks.cfg, so I can try to reproduce myself. I did a test like this: sdb 8:16 0 279.4G 0 disk |-sdb1 8:17 0 10G 0 part `-sdb2 8:18 0 10G 0 part [root@dell-per930-01 ~]# mdadm -CR /dev/md0 -l1 -n2 /dev/sdb1 /dev/sdb2 --assume-clean mdadm: Defaulting to version 1.2 metadata mdadm: array /dev/md0 started. [root@dell-per930-01 ~]# mdadm --stop /dev/md0 mdadm: stopped /dev/md0 [root@dell-per930-01 ~]# mdadm --zero-superblock /dev/sdb1 [root@dell-per930-01 ~]# mdadm --zero-superblock /dev/sdb2 [root@dell-per930-01 ~]# mdadm -E /dev/sdb1 mdadm: No md superblock detected on /dev/sdb1. [root@dell-per930-01 ~]# mdadm -E /dev/sdb2 mdadm: No md superblock detected on /dev/sdb2. In this way, the problem can't be reproduced. Reassigning to blivet, the installer storage library. *** Bug 2155971 has been marked as a duplicate of this bug. *** Created attachment 1935691 [details]
Installer logs
Created attachment 1935692 [details]
Screenshot of 'Report Bug'
Created attachment 1935693 [details]
Updated installer logs
mdadm-4.2-7.el8 has passed the sanity test. ------- Comment From Akanksha.J.N 2023-02-09 23:49 EDT------- The issue is not reproducible and I was able to proceed with the installation. # uname -r 4.18.0-452.el8.ppc64le # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 105G 0 disk ??sda1 8:1 0 4M 0 part ??sda2 8:2 0 1G 0 part /boot ??sda3 8:3 0 22G 0 part ? ??md126 9:126 0 22G 0 raid1 /home ??sda4 8:4 0 1K 0 part ??sda5 8:5 0 8.8G 0 part ? ??md127 9:127 0 8.8G 0 raid1 / ??sda6 8:6 0 12G 0 part [SWAP] sdb 8:16 1 14.5G 0 disk ??sdb1 8:17 1 2G 0 part nvme0n1 259:0 0 2.9T 0 disk ??nvme0n1p1 259:1 0 176G 0 part ? ??md126 9:126 0 22G 0 raid1 /home ??nvme0n1p2 259:2 0 70.1G 0 part ??md127 9:127 0 8.8G 0 raid1 / 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 (mdadm 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-2023:2998 |