* [linux-lvm] Szenario for lvmetad
@ 2014-08-19 11:52 Oliver Rath
2014-08-19 13:09 ` Peter Rajnoha
0 siblings, 1 reply; 2+ messages in thread
From: Oliver Rath @ 2014-08-19 11:52 UTC (permalink / raw)
To: LVM general discussion and development
Hi list,
does it make sense to use lvmetad in one pc with 4 disks, which are used
for lvm? Are the metadata cached in a non-lvmetad environment?
Tfh!
Oliver
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [linux-lvm] Szenario for lvmetad
2014-08-19 11:52 [linux-lvm] Szenario for lvmetad Oliver Rath
@ 2014-08-19 13:09 ` Peter Rajnoha
0 siblings, 0 replies; 2+ messages in thread
From: Peter Rajnoha @ 2014-08-19 13:09 UTC (permalink / raw)
To: rath; +Cc: LVM general discussion and development
On 08/19/2014 01:52 PM, Oliver Rath wrote:
> Hi list,
>
> does it make sense to use lvmetad in one pc with 4 disks, which are used
> for lvm? Are the metadata cached in a non-lvmetad environment?
Without lvmetad all the block devs are scanned (minus the ones that
are filtered) for each LVM command execution - there's no other persistent
cache. If you don't have numerous block disks in the system, you probably won't
lose much by switching off lvmetad.
However, LVM autoactivation depends on lvmetad use so if you disable lvmetad,
the LVM volumes must be always activated directly (either as part of bootup
script - which is normally left there in case someone disables lvmetad) or
the volumes must be activated on cmd line directly if you attach any PVs
when the system is already up and running (e.g. attaching iSCSI or FCoE
devices, flash disks, external storage...).
--
Peter
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-08-19 13:09 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-08-19 11:52 [linux-lvm] Szenario for lvmetad Oliver Rath
2014-08-19 13:09 ` Peter Rajnoha
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).