[lvm-devel] Suppress locking initialisation failure messages when --ignorelockingfailure is used

[Milan Broz]

On 02/08/2010 04:09 PM, Mike Snitzer wrote:
>>> Shouldn't rc.sysinit's "vgchange -a y --ignorelockingfailure" come
>>> _after_ root's rw remount?
>>
>> Exactly. It should also start volume monitoring etc.
>>
>> Note that monitoring need rw access (at least for status log to syslog,
>> but also if it triggers some change, it will require real lock - to perform
>> repair, snapshot resize or other action; metadata backups etc).
> 
> The monitoring gets started, by the "lvm2-monitor" service, after
> rc.sysinit.  So we should be fine there.

I was just not sure if "vgchange -a y" here tries to start monitoring or not.
If so, what happens? (lvm2-monitor init rc skript then will just restart it?)
Is it what we want?

Milan