Bug 813290

Summary: mdadm (md-detail) test occasionally fails with 'md device /dev/md125 does not appear to be active.'
Product: [Community] Virtualization Tools Reporter: Richard W.M. Jones <rjones>
Component: libguestfsAssignee: Richard W.M. Jones <rjones>
Status: CLOSED WORKSFORME QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: lersek, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-09-17 19:20:46 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 Richard W.M. Jones 2012-04-17 12:02:27 UTC
Description of problem:

On my new, fast machine, the mdadm test very occasionally fails:


PASS: test-inspect-fstab.sh
PASS: test-inspect-fstab-md.sh
PASS: test-list-filesystems.sh
PASS: test-list-md-devices.sh
libguestfs: error: md_detail: mdadm: md device /dev/md125 does not appear to be active.
FAIL: test-mdadm.sh

The error message comes from mdadm's '-D' (detail) subcommand
when the device in question returns ENODEV.

This is the sequence of events (dev == "/dev/md125"):

        int fd = open(dev, O_RDONLY);  # successful
        vers = md_get_version(fd);     # successful, and vers >= 9000
        if (ioctl(fd, GET_ARRAY_INFO, &array)<0) {
                if (errno == ENODEV)
                   ... error message is printed here ...

Version-Release number of selected component (if applicable):

libguestfs 1.17.31
mdadm-3.2.3-7.fc17.x86_64

How reproducible:

infrequently

Steps to Reproduce:
1. make -C tests/md check

Comment 1 Laszlo Ersek 2021-09-17 17:59:15 UTC
I think this may have been related to the guest kernel / mdadm utility used in the appliance. I cannot reproduce this. Can we close it?

Comment 2 Richard W.M. Jones 2021-09-17 19:20:46 UTC
This is a real old bug, and I also cannot reproduce it - closed.