diff options
| author | Peter Rajnoha <prajnoha@redhat.com> | 2014-10-14 09:56:58 +0200 |
|---|---|---|
| committer | Peter Rajnoha <prajnoha@redhat.com> | 2014-10-14 10:08:23 +0200 |
| commit | 02628413ca99648e70e38406384be69e20a2a6ce (patch) | |
| tree | af699407aca11912fa592e514a91d7b7c526feea /WHATS_NEW | |
| parent | d1bcdd7338148a887aae44149e3ea756c1df17a3 (diff) | |
| download | lvm2-02628413ca99648e70e38406384be69e20a2a6ce.tar.gz | |
systemd: remove workaround for lvm2-monitor.service's ExecStop line
Bug https://bugzilla.redhat.com/show_bug.cgi?id=843587 is handled better
now - the hang does not occur anymore. There are still error messages
issued though during shutdown if someone stops lvm2-lvmetad.service
manually that lvm2-monitor.service depends on (even during shutdown).
These errors are correct though and will point to incorrect
configuration (still having use_lvmetad=1 in lvm.conf and stopping
lvm2-lvmetad.service manually).
The workaround to prevent the hang is not needed now. So the
'--config "global{use_lvmetad=0}"' is now removed from the
lvm2-monitor.service's ExecStop line.
Diffstat (limited to 'WHATS_NEW')
| -rw-r--r-- | WHATS_NEW | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -1,5 +1,6 @@ Version 2.02.112 - ===================================== + Remove workaround for lvm2-monitor.service hang on stop if lvmetad stopped. Change vgremove to use process_each_lv_in_vg. Introduce WARN_ flags to control some metadata warning messages. Use process_each_pv in vgreduce. |