got error: broken pipe = backup storage not available
Task viewer: Backup
Output
Status
Stop
INFO: starting new backup job: vzdump 100 --mode snapshot --node frc --remove 0 --storage drobo --compress lzo
INFO: Starting Backup of VM 100 (qemu)
INFO: status = running
INFO: update VM 100: -lock backup
INFO: VM Name: frc
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating archive '/mnt/backup/dump/vzdump-qemu-100-2016_12_09-09_21_00.vma.lzo'
INFO: started backup task '6df91544-7c18-4fc7-b5f4-d79c13a8ea4c'
INFO: status: 0% (572588032/214748364800), sparse 0% (78450688), duration 3, 190/164 MB/s
INFO: status: 1% (2229927936/214748364800), sparse 0% (129884160), duration 13, 165/160 MB/s
INFO: status: 2% (4333633536/214748364800), sparse 0% (203542528), duration 25, 175/169 MB/s
INFO: status: 3% (6526468096/214748364800), sparse 0% (243449856), duration 40, 146/143 MB/s
lzop: No space left on device: <stdout>
INFO: status: 3% (8225554432/214748364800), sparse 0% (272982016), duration 52, 141/139 MB/s
ERROR: vma_queue_write: write error - Broken pipe
INFO: aborting backup job
INFO: closing file '/etc/pve/nodes/frc/qemu-server/100.conf.tmp.1614' failed - Input/output error
command 'qm unlock 100' failed: exit code 5
ERROR: Backup of VM 100 failed - vma_queue_write: write error - Broken pipe
INFO: Backup job finished with errors
TASK ERROR: job errors
Run this to see what’s up with the storage
df -h
I backup to my Drobo, it's not listed this time = didn’t mount on /mnt/backup
can’t unmount drobo /mnt/backup, locked
can’t delete /mnt/backup from storage from WebUI- locked
can’t delete from config manually:
nano /etc/pve/storage.cfg
locked
/etc/init.d/pve-cluster restart
Now I can mount Drobo on /mnt/backup , yay!!
But the test backup fails with again with ‘qm set 100 --lock backup’ failed: exit code 255
Task viewer: Backup
Output
Status
Stop
INFO: starting new backup job: vzdump 100 --mode snapshot --node frc --remove 0 --storage drobo --compress lzo
INFO: Starting Backup of VM 100 (qemu)
INFO: status = running
INFO: update VM 100: -lock backup
INFO: VM Name: frc
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating archive '/mnt/backup/dump/vzdump-qemu-100-2016_12_09-09_21_00.vma.lzo'
INFO: started backup task '6df91544-7c18-4fc7-b5f4-d79c13a8ea4c'
INFO: status: 0% (572588032/214748364800), sparse 0% (78450688), duration 3, 190/164 MB/s
INFO: status: 1% (2229927936/214748364800), sparse 0% (129884160), duration 13, 165/160 MB/s
INFO: status: 2% (4333633536/214748364800), sparse 0% (203542528), duration 25, 175/169 MB/s
INFO: status: 3% (6526468096/214748364800), sparse 0% (243449856), duration 40, 146/143 MB/s
lzop: No space left on device: <stdout>
INFO: status: 3% (8225554432/214748364800), sparse 0% (272982016), duration 52, 141/139 MB/s
ERROR: vma_queue_write: write error - Broken pipe
INFO: aborting backup job
INFO: closing file '/etc/pve/nodes/frc/qemu-server/100.conf.tmp.1614' failed - Input/output error
command 'qm unlock 100' failed: exit code 5
ERROR: Backup of VM 100 failed - vma_queue_write: write error - Broken pipe
INFO: Backup job finished with errors
TASK ERROR: job errors
Run this to see what’s up with the storage
df -h
I backup to my Drobo, it's not listed this time = didn’t mount on /mnt/backup
can’t unmount drobo /mnt/backup, locked
can’t delete /mnt/backup from storage from WebUI- locked
can’t delete from config manually:
nano /etc/pve/storage.cfg
locked
/etc/init.d/pve-cluster restart
Now I can mount Drobo on /mnt/backup , yay!!
But the test backup fails with again with ‘qm set 100 --lock backup’ failed: exit code 255