touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #39058
[Bug 1082325] Re: pvmove wipes data when issue_discards=1 on SSD
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as "Won't Fix".
** Changed in: lvm2 (Ubuntu Quantal)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1082325
Title:
pvmove wipes data when issue_discards=1 on SSD
Status in lvm2 - Logical Volume Manager:
Unknown
Status in lvm2 package in Ubuntu:
Fix Released
Status in lvm2 source package in Quantal:
Won't Fix
Status in lvm2 package in Debian:
Fix Released
Bug description:
[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 upstream fix is fairly self contained and separates discard and
move operations.
The patches can be found at:
https://lists.fedorahosted.org/pipermail/lvm2-commits/2012-June/000037.html
https://lists.fedorahosted.org/pipermail/lvm2-commits/2012-June/000038.html
https://lists.fedorahosted.org/pipermail/lvm2-commits/2012-June/000039.html
An SRU of just the upstream-*.patches from the -5 upload fix this bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/lvm2/+bug/1082325/+subscriptions