make.tmpl.in | 33 7 + 26 - 0 !
1 file changed, 7 insertions(+), 26 deletions(-)

 install

configure.in | 67 7 + 60 - 0 !
1 file changed, 7 insertions(+), 60 deletions(-)

 libs-cleanup

conf/example.conf.in | 2 1 + 1 - 0 !
lib/config/config.c | 10 4 + 6 - 0 !
2 files changed, 5 insertions(+), 7 deletions(-)

 dirs

configure.in | 6 1 + 5 - 0 !
1 file changed, 1 insertion(+), 5 deletions(-)

 force-paths

tools/lvm.c | 4 0 + 4 - 0 !
1 file changed, 4 deletions(-)

 implicit-pointer

daemons/dmeventd/.exported_symbols | 6 3 + 3 - 0 !
daemons/dmeventd/dmeventd.c | 22 11 + 11 - 0 !
daemons/dmeventd/libdevmapper-event.c | 16 8 + 8 - 0 !
3 files changed, 22 insertions(+), 22 deletions(-)

 dm-event-api

udev/10-dm.rules.in | 28 11 + 17 - 0 !
udev/11-dm-lvm.rules.in | 2 1 + 1 - 0 !
udev/13-dm-disk.rules.in | 2 1 + 1 - 0 !
udev/Makefile.in | 18 15 + 3 - 0 !
4 files changed, 28 insertions(+), 22 deletions(-)

 udev

scripts/lvm2_activation_generator_systemd_red_hat.c | 2 1 + 1 - 0 !
scripts/lvm2_cluster_activation_systemd_red_hat.service.in | 2 1 + 1 - 0 !
scripts/lvm2_clvmd_systemd_red_hat.service.in | 4 2 + 2 - 0 !
3 files changed, 4 insertions(+), 4 deletions(-)

 systemd

daemons/clvmd/clvmd-openais.c | 1 1 + 0 - 0 !
1 file changed, 1 insertion(+)

 clvmd-openais-format

udev/69-dm-lvm-metad.rules.in | 9 7 + 2 - 0 !
1 file changed, 7 insertions(+), 2 deletions(-)

 fix mdadm udev interaction

Also workaround incorrect blkid call

Patch-Name: udev-md.patch

udev/Makefile.in | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 don't run pvscan in background

Patch-Name: systemd-pvscan-background.patch

lib/metadata/metadata-exported.h | 1 1 + 0 - 0 !
lib/metadata/raid_manip.c | 8 7 + 1 - 0 !
test/shell/lvchange-raid1-writemostly.sh | 41 41 + 0 - 0 !
tools/lvchange.c | 15 15 + 0 - 0 !
4 files changed, 64 insertions(+), 1 deletion(-)

 lvchange: reject writemostly/writebehind on raid1 during resync

The MD kernel raid1 personality does no use any writemostly leg as the primary.

In case a previous linear LV holding data gets upconverted to
raid1 it becomes the primary leg of the new raid1 LV and a full
resynchronization is started to update the new legs.

No writemostly and/or writebehind setting may be allowed during
this initial, full synchronization period of this new raid1 LV
(using the lvchange(8) command), because that would change the
primary (i.e the previous linear LV) thus causing data loss.

lvchange has a bug not preventing this scenario.

Fix rejects setting writemostly and/or writebehind on resychronizing raid1 LVs.

Once we have status in the lvm2 metadata about the linear -> raid upconversion,
we may relax this constraint for other types of resynchronization
(e.g. for user requested "lvchange --resync ").

New lvchange-raid1-writemostly.sh test is added to the test suite.

Resolves: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855895