* Setting issue_discards=1 in /etc/lvm.conf (non-default) results in data loss, if pvmove is performed
on a Logical Volume which is moved to or form an SSD or other block devices which supports discards
* As this bug *directly cause a loss of user data* this fix should be uploaded to quantal (lvm2 in precise is not effected, because it does not support the issue_discards option.
[Test Case]
* Enable issue_discards=1 in /etc/lvm.conf
* Create a volumegroup with two physical volumes (at least one of these must support discards (e.g. an SSD)
* Create a test logical volume
* Create a filesystem on this logical volume
* With pvmove, move the underlying logical volume to the other physical volume
=> experience Data loss (in my experiments the whole logical volume was zeroed, checked with hexdumd /dev/vgtest/lvtest)
[Regression Potential]
* The upload 2.02.95-5ubuntu1 pulls in some other changes, however they do not seem be critical.
Comments for SRU consideration (https:/ /wiki.ubuntu. com/StableRelea seUpdates)
[Impact]
* Setting issue_discards=1 in /etc/lvm.conf (non-default) results in data loss, if pvmove is performed
on a Logical Volume which is moved to or form an SSD or other block devices which supports discards
* As this bug *directly cause a loss of user data* this fix should be uploaded to quantal (lvm2 in precise is not effected, because it does not support the issue_discards option.
[Test Case]
* Enable issue_discards=1 in /etc/lvm.conf
* Create a volumegroup with two physical volumes (at least one of these must support discards (e.g. an SSD)
* Create a test logical volume
* Create a filesystem on this logical volume
* With pvmove, move the underlying logical volume to the other physical volume
=> experience Data loss (in my experiments the whole logical volume was zeroed, checked with hexdumd /dev/vgtest/lvtest)
[Regression Potential]
* The upload 2.02.95-5ubuntu1 pulls in some other changes, however they do not seem be critical.