Package: lvm2 / 2.02.168-2
Metadata
Package | Version | Patches format |
---|---|---|
lvm2 | 2.02.168-2 | 3.0 (quilt) |
Patch series
view the series filePatch | File delta | Description |
---|---|---|
0001 install.patch | (download) |
make.tmpl.in |
33 7 + 26 - 0 ! |
install |
0002 libs cleanup.patch | (download) |
configure.in |
67 7 + 60 - 0 ! |
libs-cleanup |
0003 dirs.patch | (download) |
conf/example.conf.in |
2 1 + 1 - 0 ! |
dirs |
0004 force paths.patch | (download) |
configure.in |
6 1 + 5 - 0 ! |
force-paths |
0005 implicit pointer.patch | (download) |
tools/lvm.c |
4 0 + 4 - 0 ! |
implicit-pointer |
0006 dm event api.patch | (download) |
daemons/dmeventd/.exported_symbols |
6 3 + 3 - 0 ! |
dm-event-api |
0007 udev.patch | (download) |
udev/10-dm.rules.in |
28 11 + 17 - 0 ! |
udev |
0008 systemd.patch | (download) |
scripts/lvm2_activation_generator_systemd_red_hat.c |
2 1 + 1 - 0 ! |
systemd |
0009 clvmd openais format.patch | (download) |
daemons/clvmd/clvmd-openais.c |
1 1 + 0 - 0 ! |
clvmd-openais-format |
udev md.patch | (download) |
udev/69-dm-lvm-metad.rules.in |
9 7 + 2 - 0 ! |
fix mdadm udev interaction Also workaround incorrect blkid call Patch-Name: udev-md.patch |
systemd pvscan background.patch | (download) |
udev/Makefile.in |
2 1 + 1 - 0 ! |
don't run pvscan in background Patch-Name: systemd-pvscan-background.patch |
0012 lvchange reject writemostly writebehind on raid1 dur.patch | (download) |
lib/metadata/metadata-exported.h |
1 1 + 0 - 0 ! |
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 |