[Fedora-i18n-bugs] [Bug 736521] New: mdadm crash/oops when stopping array in installer environment

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.

Summary: mdadm crash/oops when stopping array in installer environment

https://bugzilla.redhat.com/show_bug.cgi?id=736521

           Summary: mdadm crash/oops when stopping array in installer
                    environment
           Product: Fedora
           Version: 16
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: unspecified
          Priority: unspecified
         Component: m17n-contrib
        AssignedTo: pnemade at redhat.com
        ReportedBy: dlehman at redhat.com
         QAContact: extras-qa at fedoraproject.org
                CC: pnemade at redhat.com, i18n-bugs at lists.fedoraproject.org
    Classification: Fedora
      Story Points: ---
              Type: ---


Created attachment 522014
  --> https://bugzilla.redhat.com/attachment.cgi?id=522014
syslog

Description of problem:
When trying to stop an array in the anaconda runtime environment in
f16-beta.tc1 mdadm crashes, which seems to lead to an unkillable udev-spawned
blkid process. The udev/blkid part is less clear to me than the mdadm oops.

To be clear mdadm says the array is stopped, and it appears to be stopped.
However, any subsequent mdadm commands on that array seem to hang. Also, within
a short time there is an 'add' event on md0 that triggers the unkillable blkid
trying to probe the non-existent md0.

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

How reproducible:
Always, from what I can tell

Steps to Reproduce:
1. Boot some f16-beta.tc1 media
2. switch to shell on tty2
3. deactivate any active md array

Actual results:
mdadm seems to succeed except for the crash dump in the syslog and the fact
that the stopped array is now unusable

Expected results:
array stopped successfully

Additional info:
In trying to track this down I made a custom image without
65-md-incremental.rules. I also manually started the rsyslog service from the
shell on tty2 before running any other commands.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.