Bug 1187080 - lvm2-2.02.115-1 update causes LVM internal error when CacheLVs are present
Summary: lvm2-2.02.115-1 update causes LVM internal error when CacheLVs are present
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lvm2
Version: 21
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Zdenek Kabelac
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1187147 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-29 10:18 UTC by Dannie Obbink
Modified: 2015-01-30 04:46 UTC (History)
12 users (show)

Fixed In Version: lvm2-2.02.115-2.fc21
Clone Of:
Environment:
Last Closed: 2015-01-30 04:46:15 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Dannie Obbink 2015-01-29 10:18:22 UTC
Description of problem:
After updating LVM:
- LVs using cache are not available. 
- pvdisplay, vgdisplay and lvdisplay no longer give any output.
- The following errors are displayed during boot. The boot process goes into emergency mode. 
Jan 29 10:49:59 hp9470m systemd[1]: Unit lvm2-pvscan@253:3.service entered failed state.
Jan 29 10:49:59 hp9470m systemd[1]: lvm2-pvscan@253:3.service failed.
Jan 29 10:50:00 hp9470m lvm[2718]: Internal error: LV vgSystem/lvVBoxCache has uknown feature flags 0.
Jan 29 10:50:00 hp9470m lvm[2718]: Could not format metadata for VG vgSystem.
Jan 29 10:50:00 hp9470m lvm[2718]: Update of lvmetad failed. This is a serious problem.
Jan 29 10:50:00 hp9470m lvm[2718]: It is strongly recommended that you restart lvmetad immediately.
Jan 29 10:50:00 hp9470m systemd[1]: lvm2-pvscan@253:0.service: main process exited, code=exited, status=5/NOTINSSTALLED
Jan 29 10:50:00 hp9470m systemd[1]: Failed to start LVM2 PV scan on device 253:0.

Downgrading LVM2 and device-mapper restores functionality.

Version-Release number of selected component (if applicable):
device-mapper.x86_64 - 1.02.93-1.fc21
device-mapper-event.x86_64 - 1.02.93-1.fc21
device-mapper-event-libs.x86_64 - 1.02.93-1.fc21
device-mapper-libs.x86_64 - 1.02.93-1.fc21
lvm2.x86_64 - 2.02.115-1.fc21
lvm2-libs.x86_64 - 2.02.115-1.fc21

How reproducible:
Always

Steps to Reproduce:
1. yum update
2. reboot


Actual results:
The above error appears. Some LVs are not available. Emergency mode is started.

Expected results:
The system should boot.

Additional info:
Severity set to urgent, as it causes boot failure.

Comment 1 Zdenek Kabelac 2015-01-29 10:58:11 UTC
Cache metadata missed defaults for cache_mode - fixed by using writethrough as compiled built-in define:

https://www.redhat.com/archives/lvm-devel/2015-January/msg00073.html

Comment 2 Zdenek Kabelac 2015-01-29 11:09:28 UTC
Since this could be only the case for older metadata which were always using writethrough mode - avoid any compile/run-time reconfigurability and stricly use this mode.

https://www.redhat.com/archives/lvm-devel/2015-January/msg00074.html

Comment 3 Fedora Update System 2015-01-29 11:50:35 UTC
lvm2-2.02.115-2.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/lvm2-2.02.115-2.fc21

Comment 4 Zdenek Kabelac 2015-01-29 12:35:53 UTC
*** Bug 1187147 has been marked as a duplicate of this bug. ***

Comment 5 Dannie Obbink 2015-01-29 15:12:37 UTC
You are right, I should have mentioned I was using writeback mode.

Thanks for the quick fix. I'll confirm solved once the -2 hits my mirror.

Comment 6 Fedora Update System 2015-01-30 04:46:15 UTC
lvm2-2.02.115-2.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.