Problem with pigz is that it bails out on missing symbolic links. Eg. follow
symlinks is on and cannot be disabled.
On July 10, 2015 6:51:21 AM CEST, Alexandre DERUMIER aderum...@odiso.com
wrote:
Hi,
user from pve-user mailing report than using pigz (multithread gzip),
improve a lot speed of
Aren't there solutions to this already? INotify based sync daemons (or
even just a cronjob)?
yes, it could be done like this, but it more difficult if you have a proxmox
backups running,
and in paralell rsync running. (if rsync are not fast enough, temp storage
could be full).
I would like
On Thu, Jul 9, 2015, 23:56 Alexandre DERUMIER aderum...@odiso.com wrote:
About backup,
I would like to add a new feature :
As I m always afraid of problem which can occur with network backup through
nfs (network saturated, latencies,...),
I would like to add an option, to backup to a temp
I would like to add an option, to backup to a temp storage (local ssd for
example), then send the backup async (rsync for example),
to the destination storage. (big slow storage)
Aren't there solutions to this already? INotify based sync daemons (or
even just a cronjob)?
Although if this was
But pigz needs all you CPU power do be that fast! If you have running VMs,
it will be as slow as normal gzip, or it will massively slow down the VMs.
I am really afraid this will trigger many support calls ...
Make the default number of pigz CPUs 2, this should not have much of a
CPU impact
Aren't there solutions to this already? INotify based sync daemons (or
even just a cronjob)?
yes, it could be done like this, but it more difficult if you have a proxmox
backups running,
and in paralell rsync running. (if rsync are not fast enough, temp storage
could be full).
I would
You could even make it so using pigz requires a setting in
vzdump.conf. So in GUI you still can only select gzip or lzop.
If set to gzip and vzdump.conf has pigz:on then pigz is used instead of gzip.
Most novice users are only going to use the GUI, this would reduce the
likelyhood of them
replace my previous mirror-sleep2.patch
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
https://www.mail-archive.com/qemu-devel@nongnu.org/msg309500.html
replace my old mirror-sleep2.patch,
Fam Zheng from redhat has finally fix it in a better way.
mirror-sleep1.patch mirror-sleep2.patch are not yet in qemu 2.4 master
mirror-sleep2 patch reference :
