Bug 514103 - mdadm can create a mdadm.conf that it cannot itself handle
mdadm can create a mdadm.conf that it cannot itself handle
Product: Fedora
Classification: Fedora
Component: mdadm (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Doug Ledford
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-07-27 21:17 EDT by David Shaw
Modified: 2009-12-18 04:38 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-12-18 04:38:55 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 David Shaw 2009-07-27 21:17:40 EDT
Description of problem:

When using mdadm to generate a mdadm.conf file (by doing mdadm --detail --scan > /etc/mdadm.conf), mdadm displays raid sets with metadata 1.2 as "metadata=1.02".

This metadata version is invalid, and so when that mdadm.conf file is used, mdadm continually complains with:

 mdadm: metadata format 1.02 unknown, ignored.

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


Steps to Reproduce:
1. Create a raid set with metadata version 1.2 (--metadata=1.2).
2. Generate a mdadm.conf using mdadm --detail --scan > /etc/mdadm.conf
3. Use any mdadm command and see the warning
Actual results:

The metadata value output from --detail --scan is set to 1.02, which is not a valid value.

Expected results:

The metadata value output from --detail --scan should be set to 1.2.
Comment 1 Bug Zapper 2009-11-18 07:10:56 EST
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 2 Bug Zapper 2009-12-18 04:38:55 EST
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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