Bug 465545 - problems with md raid1 v1.0 with bitmaps
problems with md raid1 v1.0 with bitmaps
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-10-03 16:03 EDT by Alexandre Oliva
Modified: 2009-12-18 01:29 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 01:29:56 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 Alexandre Oliva 2008-10-03 16:03:35 EDT
I played a bit with md raid metadata versions other than the default 0.90, expecting them to be stable and beneficial already.  How wrong I was :-)

First issue I ran into was that activated spare members of raid 1 never became fully active, even after syncing completed.  I.e., their metadata still didn't show them as active, and they were still numbered above the 0..N-1 range used by active members.  This was in spite of leaving them alone after syncing completed.

With udev-based progressive bringing up of raid devices, which often causes partial arrays to be brought up and missing devices to be completed later, most components end up in this limbo state.

Another problem I noticed had to do with saving bitmaps beore hibernation.  It just so happened that the raid 1 device containing the only physical volume of the volume group containing both the swap/suspend device and the root filesystem had bitmaps saved incorrectly or some such before hibernation, which prevented it from being brought up at all.  The kernel reported a failure to load up the bitmaps, and completely failed to bring the array up.

Since I went back to v0.90 metadata, I didn't experience this kind of problem, so this might be 1.x-only.

The work around to bring the system back up was to boot in rescue mode and zero out the superblock of the out-of-sync device.  (Actually, I just created a new array out of the same partitions).  It was fun to watch it come up from hibernation afterwards :-)
Comment 1 Chuck Ebbert 2008-10-10 03:03:05 EDT
Can you report these problems upstream?
Comment 2 Bug Zapper 2008-11-25 22:31:41 EST
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
Comment 3 Bug Zapper 2009-11-18 03:30:44 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 4 Bug Zapper 2009-12-18 01:29:56 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.