Description of problem: I ran `systemctl start docker` and then `docker-storage-setup`. Version-Release number of selected component: lvm2-2.02.150-1.fc24 Additional info: reporter: libreport-2.7.0 backtrace_rating: 4 cmdline: lvs --noheadings -o vg_name /dev/mapper/fedora_tomservo-root crash_function: dm_task_destroy executable: /usr/sbin/lvm global_pid: 1440 kernel: 4.5.3-300.fc24.x86_64 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reproducible: Not sure how to reproduce the problem runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (10 frames) #0 dm_task_destroy at ioctl/libdm-iface.c:474 #1 device_is_usable at activate/dev_manager.c:654 #2 _passes_usable_filter at filters/filter-usable.c:143 #3 _and_p at filters/filter-composite.c:24 #4 _and_p_with_dev_ext_info at filters/filter-composite.c:35 #5 _and_p at filters/filter-composite.c:24 #6 dev_iter_get at device/dev-cache.c:1506 #7 lvmcache_label_scan at cache/lvmcache.c:815 #8 lvmcache_get_vgnameids at cache/lvmcache.c:971 #9 get_vgnameids at metadata/metadata.c:5063
Created attachment 1157586 [details] File: backtrace
Created attachment 1157587 [details] File: cgroup
Created attachment 1157588 [details] File: core_backtrace
Created attachment 1157589 [details] File: dso_list
Created attachment 1157590 [details] File: environ
Created attachment 1157591 [details] File: exploitable
Created attachment 1157592 [details] File: limits
Created attachment 1157593 [details] File: maps
Created attachment 1157594 [details] File: mountinfo
Created attachment 1157595 [details] File: namespaces
Created attachment 1157596 [details] File: open_fds
Created attachment 1157597 [details] File: proc_pid_status
Created attachment 1157598 [details] File: var_log_messages
*** Bug 1338897 has been marked as a duplicate of this bug. ***
Fixed with upstream commit 99e96f3ce9d14e30b7150d3d4614cf9ab810e264 https://www.redhat.com/archives/lvm-devel/2016-April/msg00108.html (released in version 2.02.151)
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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.