mdadm in precise does not allow internal bitmap on version 1.2 arrays

Bug #1022915 reported by costin on 2012-07-10
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
mdadm (Debian)
Fix Released
Unknown
mdadm (Ubuntu)
Undecided
Unassigned
Precise
Medium
Dimitri John Ledkov
Quantal
Undecided
Unassigned

Bug Description

[TEST CASE]
(culled from Debian bug report)
Assuming /dev/vdb and /dev/vdc are blank devices (BE CAREFUL!):

# dd if=/dev/zero bs=1M count=100 of=/dev/vdb
# dd if=/dev/zero bs=1M count=100 of=/dev/vdc
# mdadm -C -l 1 -n 2 -e 1 --assume-clean /dev/md0 /dev/vdb /dev/vdc
mdadm: array /dev/md0 started.
# mdadm -G -b internal /dev/md0
mdadm: failed to set internal bitmap.

A fixed version should not fail to set the internal bitmap
--------
see debian bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664088

how do i get this fixed in 12.04 LTS? do i just revert to using my good old debian stable or will someone care about this bug i've encountered just ten minutes after my first meeting with ubuntu lts?

(my concern being: if only ten minutes i've run into this bug, god knows how many will i discover later on this production box?)

summary: - mdadm prior to 3.2.4 does not allow internal bitmap on version 1.2
- arrays
+ mdadm prior to 3.2.4 (shipped in in 12.04 LTS) does not allow internal
+ bitmap on version 1.2 arrays
costin (costin) on 2012-07-10
summary: - mdadm prior to 3.2.4 (shipped in in 12.04 LTS) does not allow internal
+ mdadm prior to 3.2.4 (shipped in 12.04 LTS) does not allow internal
bitmap on version 1.2 arrays
Changed in mdadm (Ubuntu Quantal):
status: New → Fix Released
Changed in mdadm (Ubuntu Precise):
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → Dmitrijs Ledkovs (dmitrij.ledkov)
milestone: none → ubuntu-12.04.1
summary: - mdadm prior to 3.2.4 (shipped in 12.04 LTS) does not allow internal
- bitmap on version 1.2 arrays
+ mdadm in precise does not allow internal bitmap on version 1.2 arrays
Stéphane Graber (stgraber) wrote :

Is this still going to land on time for 12.04.1?

Changed in mdadm (Ubuntu Precise):
status: Confirmed → Triaged
Changed in mdadm (Ubuntu Precise):
status: Triaged → In Progress
description: updated
Changed in mdadm (Debian):
status: Unknown → Fix Released

Hello costin, or anyone else affected,

Accepted mdadm into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/mdadm/3.2.5-1ubuntu0.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in mdadm (Ubuntu Precise):
status: In Progress → Fix Committed
tags: added: verification-needed
costin (costin) wrote :
Download full text (3.8 KiB)

root@imap:~# apt-get install mdadm/precise-proposed
Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version '3.2.5-1ubuntu0.1' (Ubuntu:12.04/precise-proposed [amd64]) for 'mdadm'
The following packages were automatically installed and are no longer required:
  libcrypt-openssl-random-perl libcrypt-passwdmd5-perl
Use 'apt-get autoremove' to remove them.
The following packages will be DOWNGRADED:
  mdadm
0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 28 not upgraded.
Need to get 520 kB of archives.
After this operation, 1,024 B disk space will be freed.
Do you want to continue [Y/n]? y
Get:1 http://archive.ubuntu.com/ubuntu/ precise-proposed/main mdadm amd64 3.2.5-1ubuntu0.1 [520 kB]
Fetched 520 kB in 1s (416 kB/s)
Preconfiguring packages ...
dpkg: warning: downgrading mdadm from 3.2.5-1ubuntu2 to 3.2.5-1ubuntu0.1.
(Reading database ... 63219 files and directories currently installed.)
Preparing to replace mdadm 3.2.5-1ubuntu2 (using .../mdadm_3.2.5-1ubuntu0.1_amd64.deb) ...
 * Stopping MD monitoring service mdadm --monitor
   ...done.
Unpacking replacement mdadm ...
Processing triggers for man-db ...
Processing triggers for ureadahead ...
ureadahead will be reprofiled on next reboot
Setting up mdadm (3.2.5-1ubuntu0.1) ...
Installing new version of config file /etc/logcheck/ignore.d.server/mdadm ...
 Removing any system startup links for /etc/init.d/mdadm-raid ...
update-initramfs: deferring update (trigger activated)
 * Starting MD monitoring service mdadm --monitor
   ...done.
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-3.2.0-27-generic
localepurge: Disk space freed in /usr/share/locale: 0 KiB
localepurge: Disk space freed in /usr/share/man: 0 KiB
localepurge: Disk space freed in /usr/share/gnome/help: 0 KiB
localepurge: Disk space freed in /usr/share/omf: 0 KiB

Total disk space freed by localepurge: 0 KiB

root@imap:~# mdadm -V
mdadm - v3.2.5 - 18th May 2012
root@imap:~# dpkg -l|grep mdadm
ii mdadm 3.2.5-1ubuntu0.1 tool to administer Linux MD arrays (software RAID)

root@imap:~# apt-show-versions |grep mdadm
mdadm/precise-proposed uptodate 3.2.5-1ubuntu0.1
root@imap:~# dd if=/dev/zero of=/tmp/left bs=1M count=16
16+0 records in
16+0 records out
16777216 bytes (17 MB) copied, 0.0173897 s, 965 MB/s
root@imap:~# dd if=/dev/zero of=/tmp/right bs=1M count=16
16+0 records in
16+0 records out
16777216 bytes (17 MB) copied, 0.0171915 s, 976 MB/s
root@imap:~# losetup /dev/loop0 /tmp/left
root@imap:~# losetup /dev/loop1 /tmp/right

root@imap:~# mdadm --create /dev/md/test -l 1 -n 2 /dev/loop0 /dev/loop1
mdadm: Note: this array has metadata at the start and
    may not be suitable as a boot device. If you plan to
    store '/boot' on this device please ensure that
    your boot-loader understands md/v1.x metadata, or use
    --metadata=0.90
Continue creating array? y
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md/test started.
root@imap:~# mdadm -G /dev/md/test -b internal
root@imap:~# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [r...

Read more...

tags: added: verification-done
removed: verification-needed
Adam Conrad (adconrad) wrote :

Hello costin, or anyone else affected,

Accepted mdadm into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/mdadm/3.2.5-1ubuntu0.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

tags: removed: verification-done
tags: added: verification-needed
costin (costin) on 2012-08-04
tags: added: verification-done
removed: verification-needed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mdadm - 3.2.5-1ubuntu0.2

---------------
mdadm (3.2.5-1ubuntu0.2) precise-proposed; urgency=low

  * Patch udev-md-raid.rules to not auto-start arrays based on detection
    of ddf or isw (imsm) signatures; this conflicts with dmraid usage in
    precise and requires more analysis before it can be enabled in SRU.
    LP: #1030292.

mdadm (3.2.5-1ubuntu0.1) precise-proposed; urgency=low

  * Stable Micro Point Bug Fix release:
    - SRU master bug (LP: #1009973)
    - Fixes segfault upon update-initramfs (LP: #969384)
    - Fixes does not allow internal bitmap on version 1.2 arrays (LP: #1022915)
  * Preserved previous behaviour, by reverting:
    - bitmap chunk size of 0 will continue to mean 512B
    - Modify the below fix, to accept previous syntax
      "b10c663 config: fix handing of 'homehost' in AUTO line."
  * Use upstream version of udev rules, instead of three slightly
    different ubuntu udev rules (LP: #968074) (LP: #1002357)
  * Add missing mdmon utility. This enables external metadata RAID
    formats: DDF and Intel Matrix Storage Management (IMSM). (LP: #957494)
  * Copy udev rule from /etc/udev/rules.d/ as well as the
    /lib/udev/rules.d/, to allow local administrator to override mdadm
    rules file (LP: #1017407)
  * debian/initramfs/local-premount: add call wait_for_udev to wait a
    little longer for RAID devices to appear. This improves
    boot reliability. (LP: #942106)

mdadm (3.2.5-1) unstable; urgency=low

  [ Michael Tokarev ]
  * new upstream (bugfix) release, fixing regression when --add'ing
    device to an array, introduced in 3.2.4, plus other minor fixes
    (Closes: #673104, #673344)
  * new patch: sha1-includes.diff to fix #include mess in new sha1.h
  * added a check into debian/checkarray to skip checking arrays created
    less than 2 weeks ago (Closes: #624273)

  [ Dmitrijs Ledkovs ]
  * Remove obsolete documentation dating back to ~etch release
  * Remove reference to obsolete documention from debconf templates
  * Update debconf templates translations
  * Remove compatability with acient initramfs-tools
  * Remove debian-specific mdadm-startall.8 in clean target

mdadm (3.2.4-1) unstable; urgency=low

  * new upstream (bugfix) release (Closes: #664088, #661552)
  * removed debian-run-udev.diff (applied upstream), and
    all RUNDIR handling from debian/rules (it is the default now)
  * add build-arch and build-indep targets to debian/rules, and
    bump Standards-Version to 3.9.3

mdadm (3.2.3-3) unstable; urgency=low

  * switch from topgit to plain 3.0 (quilt) layout, creating
    debian/patches. Don't build-depend on quilt as patching
    is done automatically by dpkg-source.
  * debian/patches/debian-run-udev.diff by Roger Leigh (Closes: #644319, #627774)
  * update debian/mdadm.logcheck.ignore.server to recognize "k" in
    addition of "blocks" in kernel messages. Thanks to Frédéric Brière
    for the patch (Closes: #656038)
 -- Steve Langasek <email address hidden> Fri, 03 Aug 2012 23:08:39 -0700

Changed in mdadm (Ubuntu Precise):
status: Fix Committed → Fix Released

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.