| Anonymous | Login | Signup for a new account | 2009-11-21 22:20 UTC |
| Main | My View | View Issues | Roadmap | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | |||||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| 0003989 | [CentOS-5] initscripts | block | always | 2009-11-06 15:58 | 2009-11-19 22:10 | |||||||
| Reporter | macchese | View Status | public | |||||||||
| Assigned To | ||||||||||||
| Priority | normal | Resolution | open | |||||||||
| Status | new | Product Version | 5.4 | |||||||||
| Summary | 0003989: multipathd should start before lvm2-monitor | |||||||||||
| Description |
starting on boot multipathd after lvm2-monitor causes the latter to wait undefinitely trying to scan VG, if these ones are multipathed on a SAN. Starting manually multipathd unblock lvm2-monitor and the system comes up cleanly |
|||||||||||
| Additional Information |
How to reproduce: 1) Have a FC SAN multipathed device on which create a VG/LV 2) boot in single mode 3) manually starts network (/etc/init.d/network start) 4) manually starts sshd (/etc/init.d/network/sshd start) 5) log in by ssh 6) have a look at the list of precesses (ps ax): there should be a "vgs --noheadings -o name" 7) manually starts multipathd (/etc/init.d/multipathd start) I suggest to invert the boot order of lvm2-monitor and multipathd |
|||||||||||
| Tags | 5.3, 5.4, lvm2 | |||||||||||
| Attached Files | ||||||||||||
|
|
||||||||||||
 Relationships |
|
|
Notes |
|
|
(0010310) macchese (reporter) 2009-11-07 20:23 |
sorry, I remembered that my conf is that LVM2 is set up in cluster mode and, at the time lvm2-monitor starts the cluster stack (cman, clvmd, fence,...) is not yet executed. Unfortunately I have no logs because syslogd is not yet started |
|
(0010363) macchese (reporter) 2009-11-13 11:41 |
I resolved this problem moving /etc/rc3.d/S02lvm2-monitor to /etc/rc3.d/S07lvm2-monitor. In this way lvm2-monitor starts after multipathd and can check all the VG related to dm's. Before that lvm2-monitor waited undefinitely because some VG were "on" some multipathed dm's and the multipathd daemon was not yet started |
|
(0010373) macchese (reporter) 2009-11-16 16:39 |
this is the patch that fixes my problem: --- lvm2-monitor 2009-11-16 15:27:05.000000000 +0100 +++ lvm2-monitor.orig 2009-11-16 15:26:34.000000000 +0100 @@ -15,7 +15,7 @@ # devices that were created using the -m option of lvcreate. # # -# chkconfig: 12345 07 99 +# chkconfig: 12345 02 99 # description: Starts and stops dmeventd monitoring for lvm2 # ### BEGIN INIT INFO |
|
(0010385) macchese (reporter) 2009-11-19 22:10 |
sorry, the correct category is "lvm2" and not "initscripts". I don't know how to change it |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2009-11-06 15:58 | macchese | New Issue | |
| 2009-11-06 15:58 | macchese | Assigned To | => kbsingh@karan.org |
| 2009-11-07 20:23 | macchese | Note Added: 0010310 | |
| 2009-11-13 11:41 | macchese | Note Added: 0010363 | |
| 2009-11-16 16:39 | macchese | Note Added: 0010373 | |
| 2009-11-19 22:09 | macchese | Tag Attached: 5.3 | |
| 2009-11-19 22:09 | macchese | Tag Attached: 5.4 | |
| 2009-11-19 22:09 | macchese | Tag Attached: lvm2 | |
| 2009-11-19 22:10 | macchese | Note Added: 0010385 | |
| Copyright © 2000 - 2009 Mantis Group |  |
