Bug 813290 - mdadm (md-detail) test occasionally fails with 'md device /dev/md125 does not appear to be active.'
mdadm (md-detail) test occasionally fails with 'md device /dev/md125 does not...
Status: NEW
Product: Virtualization Tools
Classification: Community
Component: libguestfs (Show other bugs)
unspecified
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Richard W.M. Jones
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-04-17 08:02 EDT by Richard W.M. Jones
Modified: 2014-09-07 18:58 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Richard W.M. Jones 2012-04-17 08:02:27 EDT
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

Note You need to log in before you can comment on or make changes to this bug.