On Aug 25, 2014, at 11:45 AM, Elvin Cako wrote:
Thanks for trying LVM caching. My first guess is that not all the devices are visible to LVM when it tries to construct the LVs. This could have been due to MD running after lvmetad - I'm not sure. However, testing without lvmetad (as you have done) should have yielded different results then. Even without the devices being visible, 'vgchange' should not crash. We could use a couple pieces of information: 1) what is the verbose trace of 'vgchange -ay'? (Add '-vvvv' for "very verbose" and capture the output.) 2) What do you mean by "crash"? Does the system go down? Does the command hang or segfault? brassow |
_______________________________________________ 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/
