Skip to main content

Backup transport errors. Transfer aborted. No space left on device?

Comments

8 comments

  • 24x7server
    Hi, No space left on device clearly means that the disk space is the issue. #df -h #df -hi Can you provide the output of the above 2 commands here..
    0
  • kabatak
    Hi, No space left on device clearly means that the disk space is the issue. #df -h #df -hi Can you provide the output of the above 2 commands here..

    Hello, here's the output: root@xxxxx:~# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda1 461G 278G 160G 64% / tmpfs 991M 0 991M 0% /lib/init/rw udev 10M 148K 9.9M 2% /dev tmpfs 991M 0 991M 0% /dev/shm root@xxxxx:~# df -hi Filesystem Inodes IUsed IFree IUse% Mounted on /dev/sda1 29M 75K 29M 1% / tmpfs 248K 5 248K 1% /lib/init/rw udev 248K 2.2K 246K 1% /dev tmpfs 248K 1 248K 1% /dev/shm
    0
  • cPanelLauren
    Hi @kabatak Is there any quotas in place on the destination server? If you have root access you can run sun something like: repquota -a
    Also, is this occurring for all accounts or just one? Thanks!
    0
  • kabatak
    Hi @kabatak Is there any quotas in place on the destination server? If you have root access you can run sun something like: repquota -a
    Also, is this occurring for all accounts or just one? Thanks!

    I got "-bash: repquota: command not found" error running that command. This is Debian btw. The "No space left on device" error appears to be happening on many accounts but not all of it.
    0
  • cPanelLauren
    Hi @kabatak The error does clearly sound like it's a space issue though I can see that it seems you have enough space. To look into this further could you please open a ticket using the link in my signature? Once open please reply with the ticket ID so that we can follow up here with the outcome of the ticket. Thanks!
    0
  • kabatak
    @cPanelLauren. I created a ticket 9924671. Thanks!
    0
  • cPanelLauren
    Thanks @kabatak, I found your ticket and I'm now following it, I also noted it with the output of df you provided earlier. I'll update here when there's new information to report. Thanks!
    0
  • cPanelLauren
    Hi @kabatak We looked into this issue and it does indeed appear that the backup server was running out of space. The issue is that the backups that are transported are almost the same size as the available space in the destination server - The scheduled backups generated are 150GB and 158GB: [05:55:38 server root@9924671 ~]cPs# du -shx /backup/weekly/2018-07-* 158G /backup/weekly/2018-07-07 150G /backup/weekly/2018-07-14
    Because the pruning operation takes place after the successful transfer the server was indeed running out of space. Please let us know if you have any questions or concerns in regard to this! Thanks! [COLOR=rgb(0, 0, 0)]
    0

Please sign in to leave a comment.