OpenVZ Forum - RDF feed
type: channel
items: How to convert back to simfs from ploop.
items: Re: How to convert back to simfs from ploop.

How to convert back to simfs from ploop.
type: item
description: How to convert back to simfs from ploop? Could somebody please point me to the documentation. Looks like my googlin skill lack today. Thank you.
creator: piplite
date: 2014-02-07T19:55:58-00:00

Re: How to convert back to simfs from ploop.
type: item
description: I did not found an answer on this question on google and also want to know how this is possible. For now i did the following trick: While running the VM with ploop, copied root/vpsid elsewhere. Make sure you stop all services on the VM. Then destroyed the VM and created a new one with simfs, copied back the data and VM started. All works fine. Our VirtualManager control panel does not work with ploop VPS's. And did not know that suddenly openvz defaults to the ploop layout. I had to modify the vz.conf. And i do not like ploop at all Regards, Danny.
creator: lx_danny
date: 2014-04-18T16:09:34-00:00

Re: How to convert back to simfs from ploop.
type: item
description: I don't recommend doing such things wile the VM is running. A safer way of reaching the VM contents is described here (advice for editing is applicable to content migration in this case): http://forum.openvz.org/index.php?t=msg&th=12585&got o=51261&#msg_51261
creator: Ales
date: 2014-04-19T23:32:35-00:00

Re: How to convert back to simfs from ploop.
type: item
description: Hello, Not sure if you got your issue solved but when doing a migration from openvz to proxmox I feel into the need for converting ploop disks to simfs since proxmox does not support ploop yet (not considered as stable). For that, I adapted a script with the opposite goal (convert simfs to ploop) and this worker well for me in many containers. Here's the gist (sorry, still can't post links): gist.github.com/dlage/8dd97c285e2dd41f58c2 There were two containers in which this failed with "Disk quota exceeded" but turned out the issue was that both had maxed out the inodes and it hadn't been saved to config (probably I just set the values with vzctl and forgot the --save flag) - fixed that and it worked.
creator: dlage
date: 2014-07-13T14:47:58-00:00