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

[Ron Leach]

On 04/07/2015 18:10, Joe Steele wrote:
> 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.
>
>
> 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.)


Joe, the problem was indeed the mount.

For some reason the destination had become disconnected from the 
source.  I don't know whether the source lost the connection, or the 
destination lost its connectivity but the result was that the source 
could not see the destination.  The error didn't exactly say that, so 
I guess there is something in 'NFS' that doesn't return 'doesn't 
exist' and instead returns something else (maybe free space = 0 ?), 
potentially misleading rdiff-backup into issuing error 28.

The 2nd problem you saw, of logging the first error, was caused for 
the same reason, the logs are stored in the destination, and the 
destination wasn't there.

I've fixed the connectivity, remounted on both servers, and 
successfully completed a backup.

Thanks to everyone who helped,

regards, Ron