You wrote: my root filesystem (/) is read-only. That's what I was reacting to. With a read-only root, if /etc/lvm/cache/ is being used and is wrong it will be unable to correct itself. You must either make the cache file writeable or delete it. vgchange -ay and vgchange -ay XXX behave differently. The first activates all VGs it sees, respecting the cache file if it exists. But with the second, if after doing that (and unless trustcache is set) it can't find XXX, it considers the cache file might be wrong and tries again without it, updating it afterwards iff write_cache_file is set. Whether or not to preserve that file across boot depends on your system, but typically vgscan will be run each time to regenerate it. Alasdair -- agk@redhat.com _______________________________________________ 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/
