Bug 995350
| Summary: | Failed to start Monitoring of LVM2 mirrors, snapshots etc. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Himanshu Garg <hgarg.india> | ||||||
| Component: | lvm2 | Assignee: | Peter Rajnoha <prajnoha> | ||||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 19 | CC: | agk, bmarzins, bmr, dwysocha, heinzm, hgarg.india, jonathan, lvm-team, msnitzer, prajnoha, prockai, zkabelac | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-06-09 13:40:35 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Updated lvm2 Now: lvm2-2.02.98-11.fc19.x86_64 But still the problem persists. Please, send the output of "lvmdump -u -l" command (a tarball with LVM context and diagnostic info). Thanks. Created attachment 788865 [details]
lvmdump
This is lvmdump tarball.
Updated lvm2: lvm2-2.02.98-12.fc19.x86_64 But still the problem persists. Updated: lvm2-2.02.98-13.fc19.x86_64 But problem still persists. Created attachment 833144 [details]
lvmdump 05 Dec 2013
Is this still reproducible with latest lvm2 package? (lvm2-2.02.98-15.fc19) Or even in Fedora 20 (if you already upgraded in the meantime)? If yes, could you please edit /lib/systemd/system/lvm2-monitor.service and add -vvvv option (verbose log) to the vgchange --monitor y command on the ExecStart line like this: ExecStart=/usr/sbin/lvm vgchange --monitor y -vvvv The reboot the machine and paste the log here please: systemctl status -l -n 100000 lvm2-monitor.service Thanks. Problem is not there in Fedora 20 with lvm2-2.02.103-3.fc20.x86_64 Thanks. OK, I'm marking closed/nextrelease then. If the problem appears again, feel free to reopen this report. |
Description of problem: Sometimes, not always, I get the error message at boot: lvm2-monitor.service - Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling Loaded: loaded (/usr/lib/systemd/system/lvm2-monitor.service; enabled) Active: failed (Result: exit-code) since Fri 2013-08-09 12:51:34 IST; 1min 5s ago Docs: man:dmeventd(8) man:lvcreate(8) man:lvchange(8) man:vgchange(8) Process: 374 ExecStart=/usr/sbin/lvm vgchange --monitor y (code=exited, status=5) Aug 09 12:51:32 server.example.com lvm[374]: /dev/sr0: open failed: No medium found Aug 09 12:51:34 server.example.com lvm[374]: 1 logical volume(s) in volume group "fedora" monitored Aug 09 12:51:34 server.example.com lvm[374]: Volume group "virtual" not found Aug 09 12:51:34 server.example.com lvm[374]: Volume group "vg_server1" not found Aug 09 12:51:34 server.example.com systemd[1]: lvm2-monitor.service: main process exited, code=exited,...LLED Aug 09 12:51:34 server.example.com systemd[1]: Failed to start Monitoring of LVM2 mirrors, snapshots e...ing. Aug 09 12:51:34 server.example.com systemd[1]: Unit lvm2-monitor.service entered failed state. Version-Release number of selected component (if applicable): lvm2-2.02.98-10.fc19.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: