[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [rdiff-backup-users] [Errno 28] No space left on device - but which

From: Joe Steele
Subject: Re: [rdiff-backup-users] [Errno 28] No space left on device - but which device?
Date: Sat, 04 Jul 2015 13:10:13 -0400
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0

On 7/4/2015 10:08 AM, Ron Leach wrote:
Exception '[Errno 28] No space left on device' raised of class '<type
   File "/var/lib/python-support/python2.5/rdiff_backup/Main.py", line
304, in error_check_Main
     try: Main(arglist)
   File "/var/lib/python-support/python2.5/rdiff_backup/Main.py", line
324, in Main
   File "/var/lib/python-support/python2.5/rdiff_backup/Main.py", line
280, in take_action
     elif action == "backup": Backup(rps[0], rps[1])
   File "/var/lib/python-support/python2.5/rdiff_backup/Main.py", line
346, in Backup
     backup.Mirror(rpin, rpout)

The above line in the trace looks suspicious. The surrounding code implies that the line would only be executed when there was no previous backup found (and yet this was to be an incremental backup). More specifically, no "/mnt/D7bkp100/Backups/rdiff-backup-data/current_mirror.*.data" file was found. Normally, rdiff-backup would not proceed with a backup if it found the rdiff-backup-data folder but no current_mirror file. It would also complain if the destination looked like a backup but had no rdiff-backup-data folder.

Since rdiff-backup didn't complain about the missing current_mirror file, the implication is that it didn't find the existing backup destination folder. In that case, it would attempt a full backup (and it doesn't look like there would be enough space for that).

All of this points to a possible mount problem at the time of the backup.

IOError while trying to log exception!
Exception '[Errno 28] No space left on device' raised of class '<type

Another error occurs while attempting to log the previous error. This time, it can't write to the log file /mnt/D7bkp100/Backups/rdiff-backup-data/backup.log. That would support the conclusion that the destination disk is the device that is full. (But if there was a problem with mounts, then it might be the root device that was full.)

If you unmount the destination device, is there anything found under its mount point on the root device?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]