gzip: stdout: No space left on device

ola

Verified User
Joined
Aug 28, 2014
Messages
16
Hi,

i get this message when performing an admin backup

Error Compressing the backup file /home/tmp/admin/admin/backup/home.tar.gz :
gzip: stdout: No space left on device
/bin/tar: /home/tmp/admin/admin/backup/home.tar.gz: Wrote only 8192 of 10240 bytes
/bin/tar: Error is not recoverable: exiting now

Error Compressing the backup file admin.root.admin.tar.gz :
gzip: stdout: No space left on device
/bin/tar: /home/tmp/admin/admin/admin.root.admin.tar.gz: Wrote only 4096 of 10240 bytes
/bin/tar: Error is not recoverable: exiting now

df -h

Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_server-lv_root
146G 12G 126G 9% /
tmpfs 3.0G 4.0K 3.0G 1% /dev/shm
/dev/vda1 485M 120M 340M 27% /boot
/dev/vdb 2.0T 407G 1.5T 22% /home/vdb

is my boot to small?
how to correct this?

regards
O
 
Hello,

What you see with

Code:
df -i
?


/boot has nothing to do with the issue.

Code:
df -i
Filesystem              Inodes  IUsed     IFree IUse% Mounted on
/dev/mapper/vg_server-lv_root
                       9674752 113880   9560872    2% /
tmpfs                   490343      2    490341    1% /dev/shm
/dev/vda1               128016     62    127954    1% /boot
/dev/vdb             134217728 300794 133916934    1% /home/vdb
 
probably problem is caused by the mounted disk /dev/vdb
in my backup i don't need this
can i exclude it?
 
You can exclude it if you need it, but from what you've told us there's no way to know if the server is trying to back this up or not.

If indeed it is included in the backup, then yes, it's probably too large, since it's 407 GB in size and there's only 126 GB of space left in /, where the /home/tmp directory is probably located.

If not the problem may be that you've run out of space for inodes. This could occur if you've got lots of small files.

Jeff
 
You can exclude it if you need it, but from what you've told us there's no way to know if the server is trying to back this up or not.

If indeed it is included in the backup, then yes, it's probably too large, since it's 407 GB in size and there's only 126 GB of space left in /, where the /home/tmp directory is probably located.

If not the problem may be that you've run out of space for inodes. This could occur if you've got lots of small files.

Jeff

Thanks for the reply.
How can i exclude /dev/vdb?
 
Is vdb a DirectAdmin usrename? If so, simply exclude it from the backup when setting it up, or edit your current backup to exclude it.

If it's not a standard DirectAdmin user, then it would depend on how you linked to it as normally it wouldn't then be backed up by Admin level backup.

Which admin backup are you using? (There are wo.)

Jeff
 
Is vdb a DirectAdmin usrename? If so, simply exclude it from the backup when setting it up, or edit your current backup to exclude it.

If it's not a standard DirectAdmin user, then it would depend on how you linked to it as normally it wouldn't then be backed up by Admin level backup.

Which admin backup are you using? (There are wo.)

Jeff

vdb is an external disk that is mounted to admin under public_html
Therefore it's not needed in the backup

im using Admin Backup/Transfer
i dont see a setting for excluding this disk

same with system backup

thanks for the help
 
Back
Top