BiT says I'm out of space when there's free space

Asked by Igor Santos

I was having trouble taking automatic snapshots or manually via GUI.
So I tried to make a backup via command line, and I got that error that's printed out in the following screenshot:
http://img217.imageshack.us/img217/9909/backintimeerror.png

After the error, the box in the right pops up, saying this: "Filesystem root has only 76MB free. You can free space by removing unused files and apps, or moving files to another disk/partition. [Examine] [ignore]". If I click "examine" it opens that Baobab window.

But, as you can see by the other windows, I DO have space. And I asked the backup to be made in the second hard drive, that is a brand new partition of 120GB in EXT4.

What's happening? =(

Question information

Language:
English Edit question
Status:
Solved
For:
Back In Time Edit question
Assignee:
No assignee Edit question
Solved by:
Dan
Solved:
Last query:
Last reply:
Revision history for this message
Dan (danleweb) said :
#1

This message does not came from BIT.
Must be a distribution specific handler when your root partition runs out of space.
This is not about you disk space on you second drive, but on the root parition.

Revision history for this message
Igor Santos (igorsantos07) said :
#2

Ok, I know it's an alert from my distro.
But the point is: I'm NOT running out of space, as you can see from the other windows.
The "out of space" error pops out every time BIT throws that error.
Why it's "ending" with my root disk space if I asked it to backup to the second drive?

Revision history for this message
Dan (danleweb) said :
#3

OK, from GParted it seems that you have about 8Gb free space on root !!! Strage. Just as a second test can you run "df -h" from command line ?

About BIT: what version are you using. If it is 0.9.26 can you upgrade to 1.0 ? (if you use Ubuntu there is a stable ppa)
BIT 1.0 log errors to help you investigate what went wrong.

Revision history for this message
Igor Santos (igorsantos07) said :
#4

~$ df -h
Sist. Arq. Size Used Avail. Use% Mounted at
/dev/sda1 15G 8,6G 5,5G 61% /
udev 1,5G 328K 1,5G 1% /dev
none 1,5G 3,7M 1,5G 1% /dev/shm
none 1,5G 336K 1,5G 1% /var/run
none 1,5G 0 1,5G 0% /var/lock
none 1,5G 0 1,5G 0% /lib/init/rw
/dev/sda6 351G 315G 36G 90% /arquivos
/dev/sda2 41G 39G 1,3G 97% /windows7
/dev/sda5 11G 8,7G 1,7G 85% /home
/dev/sdb1 111G 188M 105G 1% /media/backup

-=-=-=-=-

The log, nice idea!
I'm using BIT 1.0 already.
The log says:

[I] Take snapshot (rsync: arquivos/Downloads/Imagens SO/Ubuntu 10.04 RC desktop i386 DVD.iso)
[I] Take snapshot (rsync: arquivos/Downloads/Imagens SO/Ubuntu 10.04 RC desktop i386.iso)
[I] Take snapshot (rsync: rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32))
[E] Error: rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32)
[I] Take snapshot (rsync: rsync: write failed on "/backup/backintime/igoru-ubuntu/igoru/1/new_snapshot/backup/arquivos/Downloads/Imagens SO/Ubuntu 10.04 RC desktop i386.iso": No space left on device (28))
[E] Error: rsync: write failed on "/backup/backintime/igoru-ubuntu/igoru/1/new_snapshot/backup/arquivos/Downloads/Imagens SO/Ubuntu 10.04 RC desktop i386.iso": No space left on device (28)
[I] Take snapshot (rsync: rsync error: error in file IO (code 11) at receiver.c(302) [receiver=3.0.6])
[I] Take snapshot (rsync: rsync: connection unexpectedly closed (260849 bytes received so far) [sender])
[I] Take snapshot (rsync: rsync error: error in rsync protocol data stream (code 12) at io.c(600) [sender=3.0.6])
[E] Failed to take snapshot 13-10-2010 08:50:38 !!!

Revision history for this message
Best Dan (danleweb) said :
#5

Your snapshots folder is setup to "/backup/backintime/" and not "/media/backup/backintime/". Is this correct ? You have only 5.5 Gb on root !!!

Revision history for this message
Igor Santos (igorsantos07) said :
#6

Man, THANK YOU. haha
I didn't notice that my backup partition was misconfigured.
It was mounting to another place. The correct would be /backup.
Fixed it and BIT is working hard right now.
Hope I don't need to come back here! :D

Thank you Dan =D

Revision history for this message
Igor Santos (igorsantos07) said :
#7

Thanks Dan, that solved my question.