On Fri, Jul 11, 2008 at 10:57:31PM -0700, Daniel Stodden wrote: > I'm running, lvm2-2.02.26. Don't bother investigating that version - stuff got changed. Update to the latest release (or CVS) and try again. > Why is that data reread? Because the two parts of the code are designed to be independent. - The so-called "activation" code sits behind an API in a so-called "locking" module. There's a choice of locking modules, and some send the requests around a cluster of machines - remote machines will only run the activation code and manage the metadata independently. We just pass UUIDs through the cluster communication layer, never metadata itself. > Second: why isn't that memory freed after returning from > activate_lv? It's released after processing the whole command. If there are cases where too much is still being held while processing in the *current* version of the code, then yes, you might be able to free parts of it sooner. 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/
