Search results

  1. P

    zstd: error 25 : Write error : No space left on device (cannot write compressed block)

    Sorry if it seems like I'm trying to be annoying. I just want to help. Personally, I have now found a solution. I deleted all other containers and unnecessary files and thus had enough local space free to create another backup. Then I could use this backup to move to another server. I was...
  2. P

    zstd: error 25 : Write error : No space left on device (cannot write compressed block)

    status at this point. with rclone vfs-cache off, vzdump makes a local cache copy of the hole container -> no space left. Backup failed and container starts again. with rclone vfs-cache on, rclone makes a local cache copy of the hole container -> no space left. backup failed and container...
  3. P

    zstd: error 25 : Write error : No space left on device (cannot write compressed block)

    I used lsof |grep dump |less to find the thief ;) task\x20U 880416 root 11wW REG 0,26 0 1420 /run/vzdump.lock task\x20U 880416 root 12w REG 253,1 414 1836263...
  4. P

    zstd: error 25 : Write error : No space left on device (cannot write compressed block)

    I would expect at stop mode to ignore the --tmpdir parameter. How could to simulate a full directory? Yes, I'm sure. I cut the last line with df last time, sorry. root@pve01:~# df -h Filesystem Size Used Avail Use% Mounted on udev 2.9G 0 2.9G 0% /dev tmpfs...
  5. P

    zstd: error 25 : Write error : No space left on device (cannot write compressed block)

    I try to simulate this problem: mknod full c 1 7 pct create 333 local:vztmpl/alpine-3.16-default_20220622_amd64.tar.xz -hostname testbackup -ostype alpine -storage local-lvm -start 1 vzdump 333 --dumpdir /mnt/pcloudbackup --mode stop --tmpdir /dev/full result: root@pve01:~# mknod full c 1 7 pct...
  6. P

    zstd: error 25 : Write error : No space left on device (cannot write compressed block)

    Still doesn't work. INFO: starting new backup job: vzdump 100 --storage pcloudbackup --node pve01 --compress zstd --notes-template '{{guestname}}' --mode stop --remove 0 INFO: Starting Backup of VM 100 (lxc) INFO: Backup started at 2022-08-01 12:10:47 INFO: status = running INFO: backup mode...
  7. P

    zstd: error 25 : Write error : No space left on device (cannot write compressed block)

    is_mountpoint was a good hint. I will try that. I'm not a friend of hook scripts. I like to have the backup storage viewable in the GUI B-) . I have also protect now the mount path with chattr -i /mnt/pcloudbackup So it should be give me an earlier error, if automount doesn't work.
  8. P

    zstd: error 25 : Write error : No space left on device (cannot write compressed block)

    I'm not 100% sure, but 2 other lxc backups working. All 3 backups starting with the same job. So, how to be sure, that the automount is working all over the time?
  9. P

    zstd: error 25 : Write error : No space left on device (cannot write compressed block)

    150 GB. The last working backup was 70 GB. So it's clear. It doesn't fit into the local disk. If I'm using a external (cloud) storage to backup, it still need the space to do a local backup?
  10. P

    zstd: error 25 : Write error : No space left on device (cannot write compressed block)

    This time, I try a local backup. Also fail. INFO: starting new backup job: vzdump 100 --storage local --remove 0 --node pve01 --compress gzip --notes-template '{{guestname}}' --mode stop INFO: Starting Backup of VM 100 (lxc) INFO: Backup started at 2022-07-26 07:16:44 INFO: status = stopped...
  11. P

    zstd: error 25 : Write error : No space left on device (cannot write compressed block)

    It is not zstd. Same with gzip. INFO: Starting Backup of VM 102 (lxc) INFO: Backup started at 2022-07-14 06:38:26 INFO: status = running INFO: backup mode: stop INFO: ionice priority: 7 INFO: CT Name: sn INFO: including mount point rootfs ('/') in backup INFO: stopping virtual guest INFO...
  12. P

    zstd: error 25 : Write error : No space left on device (cannot write compressed block)

    I have the same problem, also with containers. I guesed that this is a problem with temporary file. But with your problem with kvm VMs, this may be a problem with zstd. I think it has to do with zstd not getting rid of the data as quickly as it would like and then generating an error. To...
  13. P

    lxc Backup im Stop nutzt auch tempdir?

    Moin, seit ca. 2 Wochen funktionieren die Backups von Containern nicht immer. Die Fehlermeldung lässt auf das Volllaufen des temporären Verzeichnis schließen. Doch habe ich die Backups im stop-Modus laufen. Ich habe das so verstanden, dass dann kein temporäres Verzeichnis verwendet wird. Ist...
  14. P

    Backup des Datastores

    Wie geht an hier am besten vor, um rclone zu mounten? Als Storage steht es leider noch nicht zur Verfügung (was cool wäre) und ich müsste es also wie hier besprieben: https://rclone.org/commands/rclone_mount/ direkt einmounten. Ist das wirklich der beste Weg oder könnte man mit einer Art...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!