lp://staging/ubuntu/precise-proposed/mdadm
- Get this branch:
- bzr branch lp://staging/ubuntu/precise-proposed/mdadm
Branch merges
Branch information
Recent revisions
- 65. By Steve Langasek
-
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. - 64. By Dimitri John Ledkov
-
* 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: DFF 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) - 63. By Clint Byrum
-
* Merge from Debian testing. (LP: #920324) Remaining changes:
- Call checks in local-premount to avoid race condition with udev
and opening a degraded array.
- d/initramfs/mdadm-functions : Record in /run when boot-degraded
question has been asked so that it is only asked once
- pass --test to mdadm to enable result codes for degraded arrays.
- Build udeb with -O2 on ppc64, working around a link error.
- debian/control: we need udev and util-linux in the right version. We
also remove the build dependency from quilt and docbook-to-man as both
are not used in Ubuntus mdadm.
- debian/initramfs/ hook: kept the Ubuntus version for handling the absence
of active raid arrays in <initramfs>/etc/mdadm/ mdadm.conf
- debian/initramfs/ script. local-top. DEBIAN, debian/ mdadm-startall,
debian/mdadm.raid. DEBIAN: removed. udev does its job now instead.
- debian/mdadm-startall. sgml, debian/ mdadm-startall. 8: documentation of
unused startall script
- debian/mdadm.config, debian/ mdadm.postinst - let udev do the handling
instead. Resolved merge conflict by keeping Ubuntu's version.
- debian/mdadm.postinst, debian/ mdadm.config, initramfs/ init-premount:
boot-degraded enablement; maintain udev starting of RAID devices;
init-premount hook script for the initramfs, to provide information at
boot
- debian/mkconf.in is the older mkconf. Kept the Ubuntu version.
- debian/rules: Kept Ubuntus version for installing apport hooks, not
installing un-used startall script and for adding a udev rule
corresponding to mdadm.
- debian/install-rc, check.d/_numbers, check.d/root_on_ raid: Ubuntu partman
installer changes
- debian/presubj: Dropped this unused bug reporting file. Instead use
source_mdadm.py act as an apport hook for bug handling.
- rename debian/mdadm.vol_ id.udev to debian/ mdadm.mdadm- blkid.udev so that
the rules file ends up with a more reasonable name
- d/p/debian-changes- 3.1.4-1+ 8efb9d1ubuntu4: mdadm udev rule
incrementally adds mdadm member when detected. Starting such an
array in degraded mode is possible by mdadm -IRs. Using mdadm
-ARs without stopping the array first does nothing when no
mdarray-unassociated device is available. Using mdadm -IRs to
start a previously partially assembled array through incremental
mode. Keeping the mdadm -ARs for assembling arrays which were for
some reason not assembled through incremental mode (i.e through
mdadm's udev rule). - 62. By Clint Byrum
-
* Merge from debian unstable. Remaining changes:
- Call checks in local-premount to avoid race condition with udev
and opening a degraded array.
- d/initramfs/mdadm-functions : Record in /run when boot-degraded
question has been asked so that it is only asked once
- pass --test to mdadm to enable result codes for degraded arrays.
- Build udeb with -O2 on ppc64, working around a link error.
- debian/control: we need udev and util-linux in the right version. We
also remove the build dependency from quilt and docbook-to-man as both
are not used in Ubuntus mdadm.
- debian/initramfs/ hook: kept the Ubuntus version for handling the absence
of active raid arrays in <initramfs>/etc/mdadm/ mdadm.conf
- debian/initramfs/ script. local-top. DEBIAN, debian/ mdadm-startall,
debian/mdadm.raid. DEBIAN: removed. udev does its job now instead.
- debian/mdadm-startall. sgml, debian/ mdadm-startall. 8: documentation of
unused startall script
- debian/mdadm.config, debian/ mdadm.postinst - let udev do the handling
instead. Resolved merge conflict by keeping Ubuntu's version.
- debian/mdadm.postinst, debian/ mdadm.config, initramfs/ init-premount:
boot-degraded enablement; maintain udev starting of RAID devices;
init-premount hook script for the initramfs, to provide information at
boot
- debian/mkconf.in is the older mkconf. Kept the Ubuntu version.
- debian/rules: Kept Ubuntus version for installing apport hooks, not
installing un-used startall script and for adding a udev rule
corresponding to mdadm.
- debian/install-rc, check.d/_numbers, check.d/root_on_ raid: Ubuntu partman
installer changes
- debian/presubj: Dropped this unused bug reporting file. Instead use
source_mdadm.py act as an apport hook for bug handling.
- rename debian/mdadm.vol_ id.udev to debian/ mdadm.mdadm- blkid.udev so that
the rules file ends up with a more reasonable name
- d/p/debian-changes- 3.1.4-1+ 8efb9d1ubuntu4: mdadm udev rule
incrementally adds mdadm member when detected. Starting such an
array in degraded mode is possible by mdadm -IRs. Using mdadm
-ARs without stopping the array first does nothing when no
mdarray-unassociated device is available. Using mdadm -IRs to
start a previously partially assembled array through incremental
mode. Keeping the mdadm -ARs for assembling arrays which were for
some reason not assembled through incremental mode (i.e through
mdadm's udev rule).
* Disabling -fno-strict-aliasing as according to debian bug 375876 it
has been unnecessary since mdadm 2.5.2
* Dropped changes:
- applied upstream
- d/rules: fix FTBFS by adding -Wno-unused-but-set- variable to
compiler flags until upstream solves the issue. (fixed upstream)
- d/control: add dependency on initscripts >= 2.88dsf-13.3 to ensure
/run exists per http://wiki.debian. org/ReleaseGoal s/RunDirectory
(change also done in debian)
* d/rules: add 'man' to build mdadm.8 - 61. By Clint Byrum
-
* d/initramfs/
mdadm-functions : Record in /run when boot-degraded
question has been asked so that it is only asked once (LP: #820111)
* d/control: add dependency on initscripts >= 2.88dsf-13.3 to ensure
/run exists per http://wiki.debian. org/ReleaseGoal s/RunDirectory
* d/rules: fix FTBFS by adding -Wno-unused-but-set- variable to
compiler flags until upstream solves the issue. (LP: #829463) - 60. By Clint Byrum
-
Call checks in local-premount to avoid race condition with udev
and opening a degraded array. (LP: #778520) - 58. By Surbhi Palande
-
mdadm udev rule incrementally adds mdadm member when detected. Starting
such an array in degraded mode is possible by mdadm -IRs. Using mdadm -ARs
without stopping the array first does nothing when no mdarray-unassociated
device is available. Using mdadm -IRs to start a previously partially
assembled array through incremental mode. Keeping the mdadm -ARs for
assembling arrays which were for some reason not assembled through
incremental mode (i.e through mdadm's udev rule). (LP: #728435)
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp://staging/ubuntu/quantal/mdadm