Bug 1060737
Summary: | The dm-event.service reload goes wrong - it passes failed state and completely new instance is used in the end | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Peter Rajnoha <prajnoha> |
Component: | lvm2 | Assignee: | LVM and device-mapper development team <lvm-team> |
lvm2 sub component: | Default / Unclassified | QA Contact: | cluster-qe <cluster-qe> |
Status: | CLOSED CURRENTRELEASE | Docs Contact: | |
Severity: | high | ||
Priority: | high | CC: | agk, bmarzins, bmr, cmarthal, dwysocha, heinzm, jbrassow, jonathan, lmiksik, lvm-team, msnitzer, nperic, okozina, prajnoha, prockai, thornber, zkabelac |
Version: | 7.0 | Keywords: | Triaged |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | lvm2-2.02.105-4.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 1060134 | Environment: | |
Last Closed: | 2014-06-13 11:18:31 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: |
Description
Peter Rajnoha
2014-02-03 13:34:44 UTC
The fix has been pushed upstream: https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=8a8abc5ed9358f45b127927a20f844a7ef122466 https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=fbeb08f320414cf0b5ae22096504bc4293fe939a https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=90286fa0e96dde8f79c1d06eff4a878cb3024283 https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=73f30ed6a4b85c3b70aa39efa14ce78be5bf8a3a https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=290e58b0b6f001b2f3563304fd17d606eff51ba2 To QA: to test this fix: - upgrade to new build including the fix - create some volumes that are monitored, e.g. snapshots, mirrors, thin pools - check dm-event status by calling "systemctl status dm-event" and check the "Main PID" and log messages where you should see that the volumes are monitored, check the time for reference when the volumes were registered for monitoring - run dmeventd -R to restart the daemon - check "systemctl status dm-event" again, the "Main PID" should change (as this is a new instance of dmeventd) and previously monitored devices should be reregistered for monitoring (check the log where you'll see the time has advanced which means that the monitoring registrations were reentered for new dmeventd instance). [0] rhel7-a/~ # systemctl status dm-event dm-event.service - Device-mapper event daemon Loaded: loaded (/usr/lib/systemd/system/dm-event.service; disabled) Active: active (running) since Thu 2014-02-13 05:11:11 EST; 18s ago Docs: man:dmeventd(8) Main PID: 677 (dmeventd) CGroup: /system.slice/dm-event.service `-677 /usr/sbin/dmeventd -f Feb 13 05:11:11 rhel7-a.virt systemd[1]: Starting Device-mapper event daemon... Feb 13 05:11:11 rhel7-a.virt systemd[1]: Started Device-mapper event daemon. Feb 13 05:11:11 rhel7-a.virt dmeventd[677]: dmeventd ready for processing. Feb 13 05:11:11 rhel7-a.virt lvm[677]: Monitoring snapshot vg-lvol1 Feb 13 05:11:11 rhel7-a.virt lvm[677]: Monitoring RAID device vg-lvol2 for events. Feb 13 05:11:11 rhel7-a.virt lvm[677]: Monitoring thin vg-pool-tpool. [0] rhel7-a/~ # systemctl reload dm-event.service Failed to issue method call: Job type reload is not applicable for unit dm-event.service. [0] rhel7-a/~ # dmeventd -R [0] rhel7-a/~ # systemctl status dm-event dm-event.service - Device-mapper event daemon Loaded: loaded (/usr/lib/systemd/system/dm-event.service; disabled) Active: active (running) since Thu 2014-02-13 05:11:54 EST; 3s ago Docs: man:dmeventd(8) Main PID: 1774 (dmeventd) CGroup: /system.slice/dm-event.service `-1774 /usr/sbin/dmeventd -f Feb 13 05:11:54 rhel7-a.virt systemd[1]: Starting Device-mapper event daemon... Feb 13 05:11:54 rhel7-a.virt systemd[1]: Started Device-mapper event daemon. Feb 13 05:11:54 rhel7-a.virt dmeventd[1774]: dmeventd ready for processing. Feb 13 05:11:54 rhel7-a.virt lvm[1774]: Monitoring snapshot vg-lvol1 Feb 13 05:11:54 rhel7-a.virt lvm[1774]: Monitoring RAID device vg-lvol2 for events. Feb 13 05:11:54 rhel7-a.virt lvm[1774]: Monitoring thin vg-pool-tpool. (In reply to Peter Rajnoha from comment #3) > [0] rhel7-a/~ # systemctl reload dm-event.service > Failed to issue method call: Job type reload is not applicable for unit > dm-event.service. Also, you can check that the old "systemctl reload dm-event.service" is not applicable now (as it didn't work correctly, we need to call dmeventd -R instead). Fix verified in the latest rpms. 3.10.0-113.el7.x86_64 lvm2-2.02.105-14.el7 BUILT: Wed Mar 26 08:29:41 CDT 2014 lvm2-libs-2.02.105-14.el7 BUILT: Wed Mar 26 08:29:41 CDT 2014 lvm2-cluster-2.02.105-14.el7 BUILT: Wed Mar 26 08:29:41 CDT 2014 device-mapper-1.02.84-14.el7 BUILT: Wed Mar 26 08:29:41 CDT 2014 device-mapper-libs-1.02.84-14.el7 BUILT: Wed Mar 26 08:29:41 CDT 2014 device-mapper-event-1.02.84-14.el7 BUILT: Wed Mar 26 08:29:41 CDT 2014 device-mapper-event-libs-1.02.84-14.el7 BUILT: Wed Mar 26 08:29:41 CDT 2014 device-mapper-persistent-data-0.2.8-5.el7 BUILT: Fri Feb 28 19:15:56 CST 2014 cmirror-2.02.105-14.el7 BUILT: Wed Mar 26 08:29:41 CDT 2014 [root@host-032 ~]# lvcreate -m 1 -n mirror -L 100M VG Logical volume "mirror" created [root@host-032 ~]# lvcreate -s VG/mirror -n snap1 -L 50M Rounding up size to full physical extent 52.00 MiB Logical volume "snap1" created [root@host-032 ~]# lvcreate -s VG/mirror -n snap2 -L 50M Rounding up size to full physical extent 52.00 MiB Logical volume "snap2" created [root@host-032 ~]# lvcreate --type raid1 -m 1 -L 100M -n raid VG Logical volume "raid" created [root@host-032 ~]# lvcreate --type raid1 -m 1 -L 100M -n meta VG Logical volume "meta" created [root@host-032 ~]# lvconvert --thinpool VG/raid --poolmetadata meta Logical volume "lvol0" created Converted VG/raid to thin pool. [root@host-032 ~]# lvs -a -o +devices LV VG Attr LSize Pool Origin Data% Cpy%Sync Devices [lvol0_pmspare] VG ewi------- 100.00m /dev/sda1(104) mirror VG owi-a-r--- 100.00m 100.00 mirror_rimage_0(0),mirror_rimage_1(0) [mirror_rimage_0] VG iwi-aor--- 100.00m /dev/sda1(1) [mirror_rimage_1] VG iwi-aor--- 100.00m /dev/sdb1(1) [mirror_rmeta_0] VG ewi-aor--- 4.00m /dev/sda1(0) [mirror_rmeta_1] VG ewi-aor--- 4.00m /dev/sdb1(0) raid VG twi-a-tz-- 100.00m 0.00 raid_tdata(0) [raid_tdata] VG rwi-aor--- 100.00m 100.00 raid_tdata_rimage_0(0),raid_tdata_rimage_1(0) [raid_tdata_rimage_0] VG iwi-aor--- 100.00m /dev/sda1(53) [raid_tdata_rimage_1] VG iwi-aor--- 100.00m /dev/sdb1(27) [raid_tdata_rmeta_0] VG ewi-aor--- 4.00m /dev/sda1(52) [raid_tdata_rmeta_1] VG ewi-aor--- 4.00m /dev/sdb1(26) [raid_tmeta] VG ewi-aor--- 100.00m 100.00 raid_tmeta_rimage_0(0),raid_tmeta_rimage_1(0) [raid_tmeta_rimage_0] VG iwi-aor--- 100.00m /dev/sda1(79) [raid_tmeta_rimage_1] VG iwi-aor--- 100.00m /dev/sdb1(53) [raid_tmeta_rmeta_0] VG ewi-aor--- 4.00m /dev/sda1(78) [raid_tmeta_rmeta_1] VG ewi-aor--- 4.00m /dev/sdb1(52) snap1 VG swi-a-s--- 52.00m mirror 0.00 /dev/sda1(26) snap2 VG swi-a-s--- 52.00m mirror 0.00 /dev/sda1(39) [root@host-032 ~]# systemctl status dm-event dm-event.service - Device-mapper event daemon Loaded: loaded (/usr/lib/systemd/system/dm-event.service; disabled) Active: active (running) since Wed 2014-03-26 15:53:39 CDT; 3min 41s ago Docs: man:dmeventd(8) Main PID: 2241 (dmeventd) CGroup: /system.slice/dm-event.service └─2241 /usr/sbin/dmeventd -f Mar 26 15:55:20 host-032.virt.lab.msp.redhat.com lvm[2241]: raid1 array, VG-raid, is now in-sync. Mar 26 15:55:42 host-032.virt.lab.msp.redhat.com lvm[2241]: Monitoring RAID device VG-meta for events. Mar 26 15:55:48 host-032.virt.lab.msp.redhat.com lvm[2241]: raid1 array, VG-meta, is now in-sync. Mar 26 15:56:23 host-032.virt.lab.msp.redhat.com lvm[2241]: No longer monitoring RAID device VG-raid for events. Mar 26 15:56:23 host-032.virt.lab.msp.redhat.com lvm[2241]: No longer monitoring RAID device VG-meta for events. Mar 26 15:56:23 host-032.virt.lab.msp.redhat.com lvm[2241]: Monitoring RAID device VG-meta for events. Mar 26 15:56:23 host-032.virt.lab.msp.redhat.com lvm[2241]: No longer monitoring RAID device VG-meta for events. Mar 26 15:56:24 host-032.virt.lab.msp.redhat.com lvm[2241]: Monitoring RAID device VG-raid_tdata for events. Mar 26 15:56:24 host-032.virt.lab.msp.redhat.com lvm[2241]: Monitoring RAID device VG-raid_tmeta for events. Mar 26 15:56:24 host-032.virt.lab.msp.redhat.com lvm[2241]: Monitoring thin VG-raid-tpool. [root@host-032 ~]# dmeventd -R [root@host-032 ~]# systemctl status dm-event dm-event.service - Device-mapper event daemon Loaded: loaded (/usr/lib/systemd/system/dm-event.service; disabled) Active: active (running) since Wed 2014-03-26 15:58:01 CDT; 8s ago Docs: man:dmeventd(8) Main PID: 2671 (dmeventd) CGroup: /system.slice/dm-event.service └─2671 /usr/sbin/dmeventd -f Mar 26 15:58:01 host-032.virt.lab.msp.redhat.com systemd[1]: Starting Device-mapper event daemon... Mar 26 15:58:01 host-032.virt.lab.msp.redhat.com systemd[1]: Started Device-mapper event daemon. Mar 26 15:58:01 host-032.virt.lab.msp.redhat.com dmeventd[2671]: dmeventd ready for processing. Mar 26 15:58:01 host-032.virt.lab.msp.redhat.com lvm[2671]: Monitoring snapshot VG-snap1 Mar 26 15:58:01 host-032.virt.lab.msp.redhat.com lvm[2671]: Monitoring snapshot VG-snap2 Mar 26 15:58:01 host-032.virt.lab.msp.redhat.com lvm[2671]: Monitoring RAID device VG-mirror-real for events. Mar 26 15:58:01 host-032.virt.lab.msp.redhat.com lvm[2671]: Monitoring RAID device VG-raid_tdata for events. Mar 26 15:58:01 host-032.virt.lab.msp.redhat.com lvm[2671]: Monitoring RAID device VG-raid_tmeta for events. Mar 26 15:58:01 host-032.virt.lab.msp.redhat.com lvm[2671]: Monitoring thin VG-raid-tpool. [root@host-032 ~]# systemctl reload dm-event.service Failed to issue method call: Job type reload is not applicable for unit dm-event.service. This request was resolved in Red Hat Enterprise Linux 7.0. Contact your manager or support representative in case you have further questions about the request. |