Bug 132705 - mdadm -A /dev/md$num -m $num prints super-minor warnings
Summary: mdadm -A /dev/md$num -m $num prints super-minor warnings
Alias: None
Product: Fedora
Classification: Fedora
Component: mdadm
Version: 3
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Doug Ledford
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2004-09-16 03:53 UTC by Alexandre Oliva
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2006-08-01 03:40:41 UTC

Attachments (Terms of Use)

Description Alexandre Oliva 2004-09-16 03:53:49 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2)

Description of problem:
If I attempt to bring up a raid device that's not listed in
/etc/mdadm.conf, I have to specify -m (or --super-minor).  That's
fine.  However, it's not fine that it complains about super-minor
entries for unrelated devices that are listed in /etc/mdadm.conf.

# cat /etc/mdadm.conf
DEVICE partitions
ARRAY /dev/md8 super-minor=8
ARRAY /dev/md9 super-minor=9
ARRAY /dev/md10 super-minor=10
ARRAY /dev/md6 super-minor=6
ARRAY /dev/md5 super-minor=5
# mdadm -A /dev/md0 -m 0
mdadm: only specify super-minor once, super-minor=8 ignored.
mdadm: only specify super-minor once, super-minor=9 ignored.
mdadm: only specify super-minor once, super-minor=10 ignored.
mdadm: only specify super-minor once, super-minor=6 ignored.
mdadm: only specify super-minor once, super-minor=5 ignored.
mdadm: no devices found for /dev/md0

It doesn't matter whether it finds devices or not; the warnings are
printed before it searches for them.  I don't have any inactive raid
devices atm to show the output, but I've done that before.

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

Comment 1 Matthew Miller 2006-07-10 20:18:46 UTC
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.

Thank you!

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