| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
* QA upload.
* Orphan package.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
* New upstream release
* Cherrypick patches from master up to 757e55435997e355ee9b03e5d913b5496a3c39a8.
|
| |
|
| |
|
| |
|
|
|
|
| |
installed system. Specifically, post-processed rules with full path to mdadm binary subsituted, instead of installing useless rules with the template variable BINDIR. LP: #1705215
|
|
|
|
|
|
|
| |
There isn't much for customization for mdadm --monitor.
it'll just do what it's supposed to do, so just run it.
Gbp-Pq: Name mdmonitor-service-simplify.diff
|
|
|
|
|
|
|
|
| |
This is a debian-specific change, upstream ships
the rule to use /usr/bin/readlink while on debian
it is /bin/readlink
Gbp-Pq: Name readlink-path.patch
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In 3.2.5 version of mdadm, new sha1 implementation has been included
which tries to include ansidecl.h header which is internal to some
other project. But this #include isn't really necessary, since this
implementation does not actually use any defines from ansidecl.h. So
just remove the #include, instead of adding a new external dependency.
References: http://www.spinics.net/lists/raid/msg38859.html
While at it, unconditionally include system headers like limits.h and
stdint.h, since on a Linux system these headers are available, and
these contains definitive information about real system types than
any guesses.
Gbp-Pq: Name sha1-includes.diff
|
|
|
|
|
|
|
|
|
|
| |
-Werror seems like a bad idea on released/packaged code because a toolchain
update (introducing new warnings) could break the build. We'll let upstream
use it to beautify the code, but remove it for out builds.
Signed-off-by: martin f. krafft <madduck@debian.org>
Gbp-Pq: Name debian-no-Werror.diff
|
|
|
|
|
|
|
|
|
|
|
|
| |
On Debian, the configuration file resides primarily in /etc/mdadm/mdadm.conf,
/etc/mdadm.conf is only used as a backup.
This is a Debian-specific patch.
Forwarded: not-needed
Reviewed-by: martin f. krafft <madduck@debian.org>
Gbp-Pq: Name debian-conffile-location.diff
|
|
|
|
|
|
|
|
|
|
|
| |
With commit 4b74a905a67e
("mdadm/grow: Component size must be larger than chunk size") mdadm returns
incorrect message if size given to grow was greater than 2 147 483 647 K.
Cast chunk_size to "unsigned long long" instead of casting size to "int".
Signed-off-by: Roman Sobanski <roman.sobanski@intel.com>
Signed-off-by: Jes Sorensen <jsorensen@fb.com>
Gbp-Pq: Name 0009-mdadm-grow-correct-size-and-chunk_size-casting.patch
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Block creation of the imsm volume when given size is smaller than 1M and
print appropriate message.
Commit b53bfba6119d3f6f56eb9e10e5a59da6901af159
(imsm: use rounded size for metadata initialization) introduces issue with
rounding volume sizes smaller than 1M to 0. There is an inconsistency when
size smaller than 1M was given depends of what we give as target device:
1) When block devices was given created volume has maximum available size.
2) When container symlink was given created volume has size 0. Additionally
it causes below call trace:
[69587.891556] WARNING: CPU: 28 PID: 22485 at ../drivers/md/md.c:7582 md_seq_show+0x764/0x770 [md_mod]
[69588.066405] Call Trace:
[69588.066409] seq_read+0x336/0x430
[69588.066411] proc_reg_read+0x40/0x70
[69588.066412] __vfs_read+0x26/0x140
[69588.066414] vfs_read+0x89/0x130
[69588.066415] SyS_read+0x42/0x90
[69588.066417] do_syscall_64+0x74/0x140
[69588.066419] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
Signed-off-by: Roman Sobanski <roman.sobanski@intel.com>
Signed-off-by: Jes Sorensen <jsorensen@fb.com>
Gbp-Pq: Name 0008-Prevent-create-IMSM-volume-with-size-smaller-than-1M.patch
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
mdadm assumes that blocks_per_member value is equal to num_data_stripes *
blocks_per_stripe but it is not true. For IMSM arrays created in OROM
NUM_BLOCKS_DIRTY_STRIPE_REGION sectors are added up to this value. Because
of this mdadm shows invalid size of arrays created in OROM and to fix this
we need to use array size calculation based on num data stripes and blocks
per stripe.
Signed-off-by: Mariusz Dabrowski <mariusz.dabrowski@intel.com>
Signed-off-by: Jes Sorensen <jsorensen@fb.com>
Gbp-Pq: Name 0007-imsm-do-not-use-blocks_per_member-in-array-size-calc.patch
|
|
|
|
|
|
|
|
|
|
| |
In almost every place where imsm_num_data_members is called there is
already existing map so it can be used it to avoid mistake when specifying
map for imsm_num_data_members.
Signed-off-by: Mariusz Dabrowski <mariusz.dabrowski@intel.com>
Signed-off-by: Jes Sorensen <jsorensen@fb.com>
Gbp-Pq: Name 0006-imsm-pass-already-existing-map-to-imsm_num_data_memb.patch
|
|
|
|
|
|
| |
Signed-off-by: Mariusz Dabrowski <mariusz.dabrowski@intel.com>
Signed-off-by: Jes Sorensen <jsorensen@fb.com>
Gbp-Pq: Name 0005-imsm-add-functions-to-get-and-set-imsm-dev-size.patch
|
|
|
|
|
|
|
|
|
| |
Due to compatibility to the newest OROM, imsm reserved space has to be
expanded to 4MB.
Signed-off-by: Mariusz Dabrowski <mariusz.dabrowski@intel.com>
Signed-off-by: Jes Sorensen <jsorensen@fb.com>
Gbp-Pq: Name 0004-imsm-change-reserved-space-to-4MB.patch
|
|
|
|
|
|
|
|
|
|
| |
We will never mandate an obsolete file system such as ext[2-4] for
running the test suite, nor should the test version of mdadm be
installed on the system for the tests to be run.
Signed-off-by: Jes Sorensen <jsorensen@fb.com>
Fixes: 20d10b4be873ba ("mdadm/test: Refactor and revamp 'test' script")
Gbp-Pq: Name 0003-tests-func.sh-Fix-some-total-breakage-in-the-test-sc.patch
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After 1db03765("Subdevs can't be all missing when create raid device")
raid volume can't be created with link to container. This feature should
not be blocked in Create function. IMSM code forbids creation of
container with missing disk, so case like all dev's missing is already
handled.
Permit IMSM volume creation when devices are given as link to container.
Signed-off-by: Michal Zylowski <michal.zylowski@intel.com>
Signed-off-by: Jes Sorensen <jsorensen@fb.com>
Gbp-Pq: Name 0002-imsm-Allow-create-RAID-volume-with-link-to-container.patch
|
|
|
|
|
|
|
|
| |
e->percent access the mdstat_ent which was already freed in free_mdstat
Signed-off-by: Zhipeng Xie <xiezhipeng1@huawei.com>
Signed-off-by: Jes Sorensen <jsorensen@fb.com>
Gbp-Pq: Name 0001-mdadm-fix-use-after-free-after-free_mdstat.patch
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
* Bump standards version, no changes required.
* Bump debhelper to 9.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Users of systemd with rootfs on Intel Matrix Raid and DDF external
metadata-raid arrays that require mdmon monitoring, may wish to
install dracut-core package and enable mdadm-shutdown.service. This
will create a shutdown initramfs, that systemd-shutdown can pivot
to. This may result in an improved shutdown behaviour with less hangs
and synced raid arrays. The generated initramfs will takeover mdmon
monitoring, wait for the arrays to be clean before stopping them and
unmounting everything and finally executing requested shutdown
command.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Instead have a positive message as to which arrays are included in the initramfs.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Bring in changes from Ubuntu, to make the two packages in sync:
- Drop README.Debian, quite out-of-date w.r.t. current packaging.
- debian/control - on ubuntu, downgrade default-mta from Recommends to
Suggests.
- update-grub in postinst, if available (note does not update grub1).
- drop stderr warnings in postrm.
- drop presubj, out of date, and all types of bugs are welcomed.
- on ubuntu, install apport package hook.
- on ubuntu, install incremental assembly udev rules into udeb.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
* Fix UUID= grep for configured RAIDs to be case incesetive, regression from 3.4-2.
* Re-trigger block devices at the start of local-block mdadm loop, to
re-incrementally assemble disks that appeared before RAID
personalities were registered with the kernel.
* Also, invoke non-incremental assembly of raid arrays in the
local-block loop to support running mdadm with user-exported variables
specified via param.conf.
* Closes: #830770, #830300.
|
|\ |
|
| |\ |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
rules file (#770883)
|
| | | |
|
| | | |
|