Search results

some technical elements brought here from http://forum.proxmox.com/threads/11983-OpenVZ-Ploop-support bug is caused by mysql keeping FH's open on unlinked files: https://bugzilla.openvz.org/show_bug.cgi?id=2242 a patch is out for that. However, I suspect think this will not work with rsync...

I dont think that would work - cant just suspend mysql, you need to completely shut it down. The reason is because this is the actual bug: https://bugzilla.openvz.org/show_bug.cgi?id=2242#c26 summary: mysql keeps filehandles open on unlinked (deleted) files. [facepalm] There's a patch to the...

Right now im under the belief that use of ploop for containers would solve the mysql migration issue by providing an actual filesystem image where inodes map to the same files on any host once live-migrated (vs living on the very different filesystems of the hosts). If im wrong, then we can...

Where we at with this? Seems no replies in a couple months and this is a major blocking issue. Put simply "cannot migrate typical LAMP server" which is 80% of my installs (and probably the world), and never mind if mysql is actually writing at the time or recently, it just has to be running to...

Central storage: meant NFS or the like. Complexifies things needlessly in my environment. Backup speed isnt a big deal to me right now (backing up with rsync to an old recycled target with --link-dest is pretty fast, even across 10M files (Im using linux-vserver right now) -but isnt quite a...

Im interested in ploop because of the journaling IO loads affecting other containers, as well as the snapshotting abilities. Not to mention the live migration iterative loop which uses FAM/inotify style logging (like constant data replicator) to track what was modified during the initial copy...

need https:// to access interface. easily missed/forgotten :/