[Users] vzctl compact fails to compact container, what can i do

Rene C. openvz at dokbua.com
Mon Mar 23 17:46:46 PDT 2015


Ok, so I managed to delete the vzctl snapshot without destroying anything,
now for the ploop snapshot.

# pwd
/vz/private/2202/root.hdd
# ploop snapshot-list DiskDescriptor.xml
PARENT_UUID                            C UUID
    FNAME
{00000000-0000-0000-0000-000000000000}
{1ef87f8e-e5b7-4627-8424-d2331405d712} /vz/private/2202/root.hdd/root.hdd
{1ef87f8e-e5b7-4627-8424-d2331405d712} *
{5fbaabe3-6958-40ff-92a7-860e329aab41}
/vz/private/2202/root.hdd/root.hdd.{fb7ba001-cb78-4dd3-9ac8-cb0c8cbab4f6}


So from the above I can

ploop snapshot-delete -u
5fbaabe3-6958-40ff-92a7-860e329aab41 DiskDescriptor.xml

Without destroying anything right?

What about the 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?


On Tue, Mar 24, 2015 at 12:19 AM, Kirill Kolyshkin <kolyshkin at gmail.com>
wrote:

> On 23 March 2015 at 05:35, Rene C. <openvz at dokbua.com> wrote:
> > but if I go to /vz/private/2202/root.hdd I find
> >
> > 4.0K    DiskDescriptor.xml
> > 0       DiskDescriptor.xml.lck
> > 300G    root.hdd
> > 161G    root.hdd.{8c40287b-2e17-45d1-b58f-1119b3b58b53}
> > 138G    root.hdd.{fb7ba001-cb78-4dd3-9ac8-cb0c8cbab4f6}
> >
> > It doesn't seem that there are any snapshots though, so I guess somehow
> some
> > of these files are orphans?
> >
> > # vzctl snapshot-list 2202
> > PARENT_UUID                            C UUID
> > DATE                NAME
> >                                        *
> > {a684e175-e9a0-4e22-aece-98a11081e2f0} 2014-08-10 18:00:01
> >
> > Any way I can check what is safe to delete?
>
> So, you definitely have 1 vzctl snapshots (which you are free to delete).
>
> Note that there are vzctl snapshots and there are ploop snapshots. A
> vzctl snapshot
> is a ploop snapshot plus CT config file plus CT dump (if CT was
> running while making
> a snapshot). But you can also create ploop snapshots which vzctl knows
> nothing
> about, so if you did that you have to remove such a snapshot using
> ploop command.
>
> See ploop man page for more details.
>
> As for which files are used by which snapshots, ploop snapshot-list
> will give you an idea.
>
> NOTE that if a snapshot was created by vzctl, it's best to use vzctl
> to remove it, as otherwise
> vzctl snapshot-list will list a snapshot which is no longer valid, and
> vzctl snapshot-delete
> will fail to remove it (as it's already partly removed), The last
> issue is fixed in the future
> vzctl version, but it's still better to use the tool you used to
> create snapshot to delete it.
> _______________________________________________
> Users mailing list
> Users at openvz.org
> https://lists.openvz.org/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/users/attachments/20150324/382f59ae/attachment.html>


More information about the Users mailing list