when to vgscan/pvscan/lvscan

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



(seems that this did not came through the first time?!)

Hi.

(Talking always about lvm2...)

Is there a real technical difference between pvscan, vgscan and lvscan?
I mean as far as I understand one always needs all information about
PVs,VGs and LVs in order to get the later.
So apart from different textual "debug" output, do all the same, i.e.
scanning over all configured block devices, looking for PVs and
scanning their VG-descriptors in order to get the information about al
LVs?


Is there ever the need to rund pvscan/vgscan/lvscan manually and if so
in which cases? I mean the vgscan manpage says that this happens
automatically in lvm2, so if I e.g. have my init-scripts and want to
make the LVs available, is it generally enough to do
vgchange -an
or can there be cases when the preceding vgscan is still required?


Thanks,
Philippe.

_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/


[Index of Archives]     [Gluster Users]     [Kernel Development]     [Linux Clusters]     [Device Mapper]     [Security]     [Bugtraq]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]

  Powered by Linux