There is a lot of space on that server and I did an rsync of that container
The strange thing is that at the end of the snapshot, all the files and
directories had been copied to the snapshot directory but the snapshot
process initiated by the snapshot command never got terminated. So I made
several tries to understand what was going on. Every time, after I killed
the snapshot command, the related container's snapshot directory got
deleted. That's why I reported the issue.
Like I said in a previous message, I will move all the stuff hosted on that
server to another one (ZFS) soon. So I don't really care about the problem
but may be someone else could bump on it too. I don't know.
2016-12-01 5:38 GMT-05:00 Rémy Dernat <remy...@gmail.com>:
> Just a stupid question; did you try to copy 25GB on this space with rsync
> otherwise ? I mean it could be a "not enough space" problem or any other
> issue not directly related to the snapshot itself.
> Kind regards
> 2016-12-01 11:15 GMT+01:00 Michel Dubé <m...@humanity.net>:
>> You're right, I don't use ZFS on this system. In fact, this is the first
>> LXC system I setup more than one year ago and I wanted to keep it as simple
>> as possible.
>> But I plan to move all these containers to a new server (16.04) using ZFS
>> Thanks Serge.
>> 2016-11-25 22:36 GMT-05:00 Serge Victor <dr.se...@random.re>:
>>> On Sat, Nov 26, 2016 at 9:41 AM, Michel Dubé <m...@humanity.net> wrote:
>>> > error: rsync failed: rsync: [sender] write error: Broken pipe (32)
>>> > rsync error: error in rsync protocol data stream (code 12) at io.c(837)
>>> > [sender=3.1.0]
>>> What is the underlaying filesystem? I bet you don't use ZFS or BTRFS,
>>> which have snapshotting features built-in, why?
>>> lxc-users mailing list
>> lxc-users mailing list
> lxc-users mailing list
lxc-users mailing list