850cf2857b
- SLE15 continues to use mdadm-4.0, synchronize mdadm package from
SLE12-SP3 to SLE15, re-order all patches.
- Rename the following patches, they are deleted and re-add in next
part of patches
0001-Generic-support-for-consistency-policy-and-PPL.patch
0002-Detail-show-consistency-policy.patch
0002-The-mdcheck-script-now-adds-messages-to-the-system.patch
0003-imsm-PPL-support.patch
0004-super1-PPL-support.patch
0005-Add-ppl-and-no-ppl-options-for-update.patch
0006-Grow-support-consistency-policy-change.patch
0007-udev-md-raid-assembly.rules-Skip-non-ready-devices.patch
0008-Retry-HOT_REMOVE_DISK-a-few-times.patch
0009-Introduce-sys_hot_remove_disk.patch
0010-Add-force-flag-to-hot_remove_disk.patch
0011-Detail-handle-non-existent-arrays-better.patch
- Synchronize patches from mdadm of SLE12-SP3, the above renamed
patches are re-add here,
0001-Makefile-Fix-date-to-be-output-in-ISO-format.patch
0002-imsm-fix-missing-error-message-during-migration.patch
0003-Fix-oddity-where-mdadm-did-not-recognise-a-relative-.patch
0004-mdadm-check-the-nodes-when-operate-clustered-array.patch
0005-examine-tidy-up-some-code.patch
0006-mdadm-add-man-page-for-symlinks.patch
0007-mdadm-add-checking-clustered-bitmap-in-assemble-mode.patch
0008-mdadm-Add-Wimplicit-fallthrough-0-in-Makefile.patch
0009-mdadm-Specify-enough-length-when-write-to-buffer.patch
0010-mdadm-it-doesn-t-make-sense-to-set-bitmap-twice.patch
0011-mdadm-Monitor-Fix-NULL-pointer-dereference-when-stat.patch
0012-Replace-snprintf-with-strncpy-at-some-places-to-avoi.patch
OBS-URL: https://build.opensuse.org/request/show/517978
OBS-URL: https://build.opensuse.org/package/show/Base:System/mdadm?expand=0&rev=150
43 lines
1.5 KiB
Diff
43 lines
1.5 KiB
Diff
From 5c5ea85b4deedf5e7491a905bbb4f4a3bc284f2c Mon Sep 17 00:00:00 2001
|
|
From: Alexey Obitotskiy <aleksey.obitotskiy@intel.com>
|
|
Date: Tue, 9 May 2017 12:25:43 +0200
|
|
Subject: [PATCH] imsm: allow drives in a container regardless of sector size
|
|
|
|
IMSM doesn't allow to create arrays including drives with different
|
|
sector sizes. The initial idea was not to permit to combine drives
|
|
with different sector size in the same container. The problem is it
|
|
only worked for array creation. On array assemble there are no
|
|
calls to metadata handlers to see if drive is suitable for a container
|
|
(e.g. as a spare) and it leads to wrong configuration.
|
|
|
|
Revert the change and allow adding drives with different sector size
|
|
to the container.
|
|
|
|
Signed-off-by: Alexey Obitotskiy <aleksey.obitotskiy@intel.com>
|
|
Signed-off-by: Tomasz Majchrzak <tomasz.majchrzak@intel.com>
|
|
Signed-off-by: Jes Sorensen <jsorensen@fb.com>
|
|
---
|
|
super-intel.c | 6 ------
|
|
1 file changed, 6 deletions(-)
|
|
|
|
diff --git a/super-intel.c b/super-intel.c
|
|
index e13c940..2a5d848 100644
|
|
--- a/super-intel.c
|
|
+++ b/super-intel.c
|
|
@@ -5716,12 +5716,6 @@ static int add_to_super_imsm(struct supertype *st, mdu_disk_info_t *dk,
|
|
if (super->sector_size == 0) {
|
|
/* this a first device, so sector_size is not set yet */
|
|
super->sector_size = member_sector_size;
|
|
- } else if (member_sector_size != super->sector_size) {
|
|
- pr_err("Mixing between different sector size is forbidden, aborting...\n");
|
|
- if (dd->devname)
|
|
- free(dd->devname);
|
|
- free(dd);
|
|
- return 1;
|
|
}
|
|
|
|
/* clear migr_rec when adding disk to container */
|
|
--
|
|
2.12.0
|
|
|