Thanks a lot.
It looks like that these @copy are left overs from failed container
snapshots. I'm creating an destroying snapshots via the api (pylxd) and
I've seen @copy snapshots at creation time where I expected a @snapshot
zfs snapshot. I'm now destroying these @copy snapshots automatically
(which most of the time succeeds, every now and then there's still a
@snaphot dependency that blocks the destroy).
On Thu, 2019-01-24 at 14:35 -0500, Stéphane Graber wrote:
> Hi,
>
> If ZFS lets you, then yes, but normally those will be here because
> you've created a container as a copy of this one, due to how zfs
> datasets work, that snapshot then has to remain until the container
> which was created from it is deleted.
>
> Stéphane
>
> On Wed, Jan 23, 2019 at 11:04 PM Kees Bos
> wrote:
> >
> > Hi,
> >
> >
> > I see multiple @copy snaphots on some containers (zfs)
> >
> > From https://github.com/lxc/lxd/issues/5104 it is not clear to me
> > why
> > there are multiple on a container.
> >
> > Can I safely remove these snapshots (if zfs lets me)?
> >
> >
> > Kees
> >
> > ___
> > lxc-users mailing list
> > lxc-users@lists.linuxcontainers.org
> > http://lists.linuxcontainers.org/listinfo/lxc-users
>
>
>
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users
