[rdiff-backup-users] Re: rdiff stopped working after I ran out of disk space.

[Wiebe Cazemier]

On Tuesday 15 May 2007 09:36, Tom Versluys wrote:

> Hello,
> 
> I have a rdiff script that automatically makes a backup every night.
> Because I didn't check the hard drive space every time,, I ran out of disk
> space.
> 
> Now I have cleared some space, but rdiff doesn't work anymore.
> 
> Now I get this :
> 
> /home
> Traceback (most recent call last):
>   File "/usr/bin/rdiff-backup", line 23, in ?
>     rdiff_backup.Main.Main(sys.argv[1:])
>   File "/usr/lib/python2.3/site-packages/rdiff_backup/Main.py", line 260, in
>   Main
>     take_action(rps)
>   File "/usr/lib/python2.3/site-packages/rdiff_backup/Main.py", line 238, in
>   take_action
>     elif action == "remove-older-than": RemoveOlderThan(rps[0])
>   File "/usr/lib/python2.3/site-packages/rdiff_backup/Main.py", line 716, in
>   RemoveOlderThan
>     rootrp = require_root_set(rootrp)
>   File "/usr/lib/python2.3/site-packages/rdiff_backup/Main.py", line 657, in
>   require_root_set
>     single_set_fs_globals(Globals.rbdir)
>   File "/usr/lib/python2.3/site-packages/rdiff_backup/Main.py", line 678, in
>   single_set_fs_globals
>     fsa = rbdir.conn.fs_abilities.get_fsabilities_readwrite('archive', rbdir)
>   File "/usr/lib/python2.3/site-packages/rdiff_backup/fs_abilities.py", line
>   404, in get_fsabilities_readwrite
>     return FSAbilities(desc_string).init_readwrite(
>   File "/usr/lib/python2.3/site-packages/rdiff_backup/fs_abilities.py", line
>   144, in init_readwrite
>     self.set_ownership(subdir)
>   File "/usr/lib/python2.3/site-packages/rdiff_backup/fs_abilities.py", line
>   188, in set_ownership
>     tmp_rp.touch()
>   File "/usr/lib/python2.3/site-packages/rdiff_backup/rpath.py", line 817, in
>   touch
>     self.conn.open(self.path, "w").close()
> IOError: [Errno 5] Input/output error:
> '/MSA20/1T46/planning/home/rdiff-backup-data/rdiff-backup.tmp.11/foo'
> 
> Any suggestions on how to solve this ?

An old message, but perhaps still useful.

If you can't free up any space, you might want to grow your partition and the
filesystem on it. This is a dangerous procedure, however. I never trusted
tools that do any intelligent resizing, but if you have a partition after the
one that is full, you could delete it, grow this one, and run resize2fs or
whatever tool for the filesystem you use. Still dangerous, but less so.
Experiment on something else first...

Another possibility is that when you run rdiff-backup as non-root, you still
have the reserved superuser space available. You could decrease that with
tune2fs (if you use ext3) and then run --check-destination-dir
and --remove-older-than.