<div dir="ltr"><div><br></div><div><br></div><div>Ok, so I managed to delete the vzctl snapshot without destroying anything, now for the ploop snapshot.</div><div><br></div><div><div><font face="monospace, monospace"># pwd</font></div><div><font face="monospace, monospace">/vz/private/2202/root.hdd</font></div><div><font face="monospace, monospace"># ploop snapshot-list DiskDescriptor.xml</font></div><div><font face="monospace, monospace">PARENT_UUID C UUID FNAME</font></div><div><font face="monospace, monospace">{00000000-0000-0000-0000-000000000000} {1ef87f8e-e5b7-4627-8424-d2331405d712} /vz/private/2202/root.hdd/root.hdd</font></div><div><font face="monospace, monospace">{1ef87f8e-e5b7-4627-8424-d2331405d712} * {5fbaabe3-6958-40ff-92a7-860e329aab41} /vz/private/2202/root.hdd/root.hdd.{fb7ba001-cb78-4dd3-9ac8-cb0c8cbab4f6}</font></div></div><div><br></div><div><br></div><div>So from the above I can </div><div><br></div><div><font face="monospace, monospace">ploop snapshot-delete -u 5fbaabe3-6958-40ff-92a7-860e329aab41 DiskDescriptor.xml</font></div><div><span style="font-family:monospace,monospace"><br></span></div><div><span style="font-family:monospace,monospace">Without destroying anything right?</span></div><div><span style="font-family:monospace,monospace"><br></span></div><div><span style="font-family:monospace,monospace">What about the </span><span style="font-family:monospace,monospace">1ef87f8e-e5b7-4627-8424-d2331405d712 UUID - isn't that the actual ploop partition itself? I think it's a little dangerous how it's presented by ploop, unless I am misunderstanding something?</span></div><div><span style="font-family:monospace,monospace"><br></span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 24, 2015 at 12:19 AM, Kirill Kolyshkin <span dir="ltr"><<a href="mailto:kolyshkin@gmail.com" target="_blank">kolyshkin@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 23 March 2015 at 05:35, Rene C. <<a href="mailto:openvz@dokbua.com">openvz@dokbua.com</a>> wrote:<br>
> but if I go to /vz/private/2202/root.hdd I find<br>
><br>
> 4.0K DiskDescriptor.xml<br>
> 0 DiskDescriptor.xml.lck<br>
> 300G root.hdd<br>
> 161G root.hdd.{8c40287b-2e17-45d1-b58f-1119b3b58b53}<br>
> 138G root.hdd.{fb7ba001-cb78-4dd3-9ac8-cb0c8cbab4f6}<br>
><br>
> It doesn't seem that there are any snapshots though, so I guess somehow some<br>
> of these files are orphans?<br>
><br>
> # vzctl snapshot-list 2202<br>
> PARENT_UUID C UUID<br>
> DATE NAME<br>
> *<br>
> {a684e175-e9a0-4e22-aece-98a11081e2f0} 2014-08-10 18:00:01<br>
><br>
> Any way I can check what is safe to delete?<br>
<br>
So, you definitely have 1 vzctl snapshots (which you are free to delete).<br>
<br>
Note that there are vzctl snapshots and there are ploop snapshots. A<br>
vzctl snapshot<br>
is a ploop snapshot plus CT config file plus CT dump (if CT was<br>
running while making<br>
a snapshot). But you can also create ploop snapshots which vzctl knows nothing<br>
about, so if you did that you have to remove such a snapshot using<br>
ploop command.<br>
<br>
See ploop man page for more details.<br>
<br>
As for which files are used by which snapshots, ploop snapshot-list<br>
will give you an idea.<br>
<br>
NOTE that if a snapshot was created by vzctl, it's best to use vzctl<br>
to remove it, as otherwise<br>
vzctl snapshot-list will list a snapshot which is no longer valid, and<br>
vzctl snapshot-delete<br>
will fail to remove it (as it's already partly removed), The last<br>
issue is fixed in the future<br>
vzctl version, but it's still better to use the tool you used to<br>
create snapshot to delete it.<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@openvz.org">Users@openvz.org</a><br>
<a href="https://lists.openvz.org/mailman/listinfo/users" target="_blank">https://lists.openvz.org/mailman/listinfo/users</a><br>
</blockquote></div><br></div>