Thanks for the information. I'll post that to my redhat support ticket and see if they can help me with a more immediate fix. > Anyway, multiple snapshots from the same origin can cause considerable > performance decrease (there is no shared area for snapshots in current > implementation, so write to origin will cause new writes to every snapshot > copy-on-write area). This copy on write issue had already occoured to us. We were going to roll out with the concept of a persistent or nonpersistent database instance. The nonpersistent ones were going to be removed before refreshing the data on the main database source. There is another script that recreates all the developer instances after the update is complete. Shaun
Attachment:
pgponR6HAWTxP.pgp
Description: PGP signature
_______________________________________________ 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/
