Description of problem: Here is what I did to cause the crash: -created an LVM snapshot of the root volume -changed some files -rebooted the system -decided that the changes were good -performed a merge of the snapshot with the root volume using lvconvert --merge -got an error message stating that the merge cannot be done until the system is rebooted -rebooted the system -system appeared to boot normally, except that the automatic bug reporting tool appeared. Version-Release number of selected component: lvm2-2.02.106-1.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: (lvm2) '' '' '' '' '' '' '' '' '' '' --cache --activate ay 8:2 crash_function: lv_is_merging_cow executable: /usr/sbin/lvm kernel: 3.14.4-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 lv_is_merging_cow at metadata/snapshot_manip.c:145 #1 dev_manager_snapshot_percent at activate/dev_manager.c:1013 #2 lv_snapshot_percent at activate/activate.c:775 #3 _poll_merge_progress at lvconvert.c:804 #4 _check_lv_status at polldaemon.c:76 #5 _wait_for_single_lv at polldaemon.c:155 #6 poll_daemon at polldaemon.c:287 #7 lvconvert_poll at lvconvert.c:904 #8 lv_spawn_background_polling at toollib.c:1508 #9 lv_change_activate at toollib.c:1426
Created attachment 901717 [details] File: backtrace
Created attachment 901718 [details] File: cgroup
Created attachment 901719 [details] File: core_backtrace
Created attachment 901720 [details] File: dso_list
Created attachment 901721 [details] File: environ
Created attachment 901722 [details] File: exploitable
Created attachment 901723 [details] File: limits
Created attachment 901724 [details] File: maps
Created attachment 901725 [details] File: open_fds
Created attachment 901726 [details] File: proc_pid_status
Created attachment 901727 [details] File: var_log_messages
Yep - the problem is - there are 2 paths leading to invoke of merge: -- lvconvert_poll lv_spawn_background_polling lv_refresh vg_refresh_visible _auto_activation_handler lvmetad_pv_found -- lvconvert_poll lv_spawn_background_polling lv_change_activate _activate_lvs_in_vg vgchange_activate _auto_activation_handler lvmetad_pv_found -- When one of them wins - the other fails (thought metadata are correct and consistent, since write-lock protect parallel metadata updates). We are thinking about the solution
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.