Heinz Mauelshagen 8ab0725077 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		2017-02-23 15:09:29 +01:00
..
api	tests: test should clean devices it has created	2016-12-11 23:24:19 +01:00
dbus	lvmdbustest: Print messages if timeout value > 10%	2016-12-20 11:06:57 -06:00
lib	tests: support zero_dev	2017-02-22 15:40:59 +01:00
shell	lvchange: reject writemostly/writebehind on raid1 during resync	2017-02-23 15:09:29 +01:00
unit	doc: change fsf address	2016-01-21 12:11:37 +01:00
.gitignore	test: add results/ to .gitignore	2016-12-10 18:00:25 +00:00
Makefile.in	makefiles: use configure vars	2017-02-14 10:24:56 +01:00