Search results

I even tried manual run: root@backup:~# pve-zsync sync --source 1.2.3.4:103 --dest D2 --name 103 --maxsnap 10 --method ssh ERROR: in path

It is not the main problem. Main issue is ERROR: in path I even tried creating bash from terminal. ERROR: in path still exits.

root@backup:/D4BACKUP# ./pve-zsync.sh ERROR: in path ERROR: in path ERROR: in path ... ... ./pve-zsync.sh: line 1: $'\r': command not found ./pve-zsync.sh: line 2: $'\r': command not found But some syncs are done. I just upgraded to v6. With v5 it was running fine. I am syncing to different...

But happens again next time I run.

Thank you I fixed it with your answer.

For those having same issue which I am sure many, I shrink disk in kvm then set dataset size and extend again. And dataset size dropped to in use size again.

I tried trim it only reduced a few GBs. I am going to try my method on a windows machine.

It did not make any difference. But you already gave me an idea. I will shrink disk to used size and extend it again. I feel like it will reduce dataset to used amount. What do you think?

I want to reduce size of backups taken from proxmox, snaphots by zfs and dataset size of kvms. Because as time pass by, with disk read/write/deletes, disk size increases unnecessarily. So I need release free space. Were I able to explain ?

This is what I to learn. I tried zerofilling, defragmenting disk but they do not seem to help much. Only couple of GBs is reduced. So you suggest shrink the partition to used size and extend again? Do you think if clonning kvm from proxmox might help ?

I am not using raidz. This happens with read/writes/deletes on disk. If I move data to newly installed kvm, size drops to real usage.

[root@ns34 ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT vda 252:0 0 150G 0 disk ├─vda1 252:1 0 100M 0 part /boot ├─vda2 252:2 0 30G 0 part /var ├─vda3 252:3 0 20G 0 part /usr ├─vda4 252:4 0 1K 0 part ├─vda5 252:5 0 8G 0 part [SWAP] ├─vda6 252:6 0...

From kvm: [root@ns34 ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/vda7 976M 674M 252M 73% / tmpfs 1.7G 28K 1.7G 1% /dev/shm /dev/vda1 93M 76M 13M 87% /boot /dev/vda8 88G 53G 34G 61% /home /dev/vda6 2.0G 124M 1.7G 7%...

No one ?

None of them: root@s1:~# zfs list -t snapshot no datasets available Am I missing someting? Could this be something to do inside KVM? Like defragmantation ?

I noted that older zfs dataset is more space it uses than it really does. More clearly, kvm disk has only 51.53 GB in use. When I move this dataset to new node, it moves 152 GB; root@s1:~# pve-zsync sync --source 118 --dest 1.2.3.4:D4 --verbose send from @rep_default_2019-12-08_20:59:49 to...

Ok D1 was represnting rpool/data. When I set D1 > rpool/data command run fine.

Ok on remote backup server, command is: /usr/sbin/pve-zsync sync --source 1.2.3.4:125 --dest D1 --name 125WEEKLY --maxsnap 10 --method ssh Error comes: COMMAND: ssh -o 'BatchMode=yes' root@1.2.3.4 -- zfs send -- P2/vm-125-disk-1@rep_125WEEKLY_2019-09-26_01:41:32 | zfs recv -F --...

Better than that, I am only allowing traffic only between nodes and from my pc. And my pc has dynamic ip so I update it with following bash to update ip in rules in case of ip change: updateip.sh # crontab -e : */5 * * * * sh /updateip.sh # /etc/init.d/cron restart...

Yes you are right. I am taking backup from a different datacenter / country. And initiate from remote backup server only. But good point to remind.