Bug 121076 - raidstop /dev/md0 or mdadm --stop /dev/md0 fails on 2.4.21-12EL ia64
raidstop /dev/md0 or mdadm --stop /dev/md0 fails on 2.4.21-12EL ia64
Status: CLOSED DUPLICATE of bug 119532
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: mdadm (Show other bugs)
ia64 Linux
medium Severity medium
: ---
: ---
Assigned To: Doug Ledford
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2004-04-16 17:04 EDT by Paul Clements
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 14:02:37 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Paul Clements 2004-04-16 17:04:45 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)

Description of problem:
RHEL3 Update 2 Beta ia64 

# cat /etc/redhat-release 
Red Hat Enterprise Linux AS release 3 (Taroon Update 2)

/dev/md0 cannot be stopped with raidstop or mdadm --stop (although
other md devices can be stopped), the kernel gives -EBUSY every time
an attempt is made to stop /dev/md0

Version-Release number of selected component (if applicable):
kernel-2.4.21-12.EL, raidtools-1.00.3-7, mdadm-1.5.0-3

How reproducible:

Steps to Reproduce:
# mdadm -C -l 1 -n 2 /dev/md0 /dev/loop1 /dev/loop2

# mdadm --stop /dev/md0
mdadm: fail to stop array /dev/md0: Device or resource busy

# raidstop /dev/md0
/dev/md0: Device or resource busy

(The same sequence works if the device is /dev/md1 or /dev/md2).

Additional info:
Comment 1 Paul Clements 2004-04-19 12:26:15 EDT
The problem is due to the "mdadm --monitor --scan" process that is
started at boot time (/etc/init.d/mdmonitor). If this is stopped,
/dev/md0 can then be stopped.
Comment 2 Doug Ledford 2004-04-22 18:37:30 EDT

*** This bug has been marked as a duplicate of 119532 ***
Comment 3 Red Hat Bugzilla 2006-02-21 14:02:37 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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