Skip to content

restore failed: stream closed because of a broken pipe #81

Description

@merkys7

Awesome project! Kudos

What would be the easiest way to implement retries into pmoxs3backuproxy for intermediate connection errors?
stream closed because of a broken pipe

open block backend for target '/dev/pve/vm-404119-disk-0'
starting to restore snapshot 'vm/404119/2025-09-11T08:20:40Z'
download and verify backup index
progress 1% (read 4294967296 bytes, zeroes = 10% (469762048 bytes), duration 1356 sec)
progress 2% (read 8589934592 bytes, zeroes = 6% (595591168 bytes), duration 2720 sec)
progress 3% (read 12884901888 bytes, zeroes = 5% (746586112 bytes), duration 4808 sec)
progress 4% (read 17179869184 bytes, zeroes = 4% (843055104 bytes), duration 6551 sec)
restore failed: stream closed because of a broken pipe
  Consider pruning pve VG archive with more then 221 MiB in 771 files (check archiving is needed in lvm.conf).
  Consider pruning pve VG archive with more then 216 MiB in 772 files (check archiving is needed in lvm.conf).
  Logical volume "vm-404119-disk-0" successfully removed.
temporary volume 'local-lvm:vm-404119-disk-0' successfully removed
  Consider pruning pve VG archive with more then 216 MiB in 773 files (check archiving is needed in lvm.conf).
  Consider pruning pve VG archive with more then 216 MiB in 774 files (check archiving is needed in lvm.conf).
  Logical volume "vm-404119-cloudinit" successfully removed.
temporary volume 'local-lvm:vm-404119-cloudinit' successfully removed
error before or during data restore, some or all disks were not completely restored. VM 404119 state is NOT cleaned up.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions