Bug 1135943 - Update to latest upstream release that contains important bug fixes
Summary: Update to latest upstream release that contains important bug fixes
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lvm2
Version: 21
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Peter Rajnoha
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-01 09:24 UTC by Peter Rajnoha
Modified: 2014-09-23 04:21 UTC (History)
11 users (show)

Fixed In Version: lvm2-2.02.111-1.fc21
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-23 04:21:04 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Peter Rajnoha 2014-09-01 09:24:49 UTC
LVM2 release v2.02.111 contains important fixes for regressions from v2.02.110 and other fixes:

  - Pass properly sized char buffers for sscanf when initializing clvmd.
  - Reinstate nosync logic when extending mirror. (2.02.110)
  - Fix total area extent calculation when allocating cache pool. (2.02.110)
  - Restore proper buffer size for parsing mountinfo line (1.02.89)

Include this bug-fix release in F21.

Comment 1 Fedora Update System 2014-09-01 09:41:22 UTC
lvm2-2.02.111-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/lvm2-2.02.111-1.fc21

Comment 2 Fedora Update System 2014-09-01 19:46:14 UTC
Package lvm2-2.02.111-1.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing lvm2-2.02.111-1.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-10011/lvm2-2.02.111-1.fc21
then log in and leave karma (feedback).

Comment 3 Fedora Update System 2014-09-23 04:21:04 UTC
lvm2-2.02.111-1.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.