Friday, April 5, 2013

Synology: Time Backup on DiskStation has failed. Please check the package log for further information.

Today my new Synology DS212j notified me via email about: Time Backup on DiskStation has failed. Please check the package log for further information.

Aside from the email notification and missing versions in the timeline, I could not find any indication of the error nor its reason in the general web interface nor the Time Backup web interface.

Google told me that the Time Backup package log could be found at /var/log/timebkp.log.

So I logged in via ssh and found: {WARN}{1365130850}{...}{Task [matthias] has failed to backup shared folder [matthias] due to [error occurred while copying files].} {ERR}{1365130850}{matthias}{Task [matthias] has failed to backup version [20130405-0500] due to [error occurred while copying files].}

Not very informative. However, in the sibling /var/log/timebkp.debug I found: Apr 05 00:00:54 [14260]BK_ERR:rsync return with error, return code = 41

Which led me to notify the file /var/log/rsync.error which hold the solution: Apr 05 00:00:53 (14436) [ERROR] log.c (350): rsync: recv_generator: mkdir "/volumeUSB1/usbshare/TimeBackup/..." failed: No space left on device (28)

I was first confused because the device had plenty of space left, but then realized that the ext4 file system had run out of inodes. I had originally provisioned the file system for another purpose and therefore reduced the inode count by factor 256. This and the habit of Time Backup to use lots of hard links which consume an inode per hard link had created the inode shortage.

As ext4 doesn't allow to increase the inode count I had to re-create the file system.

I plugged the hard disk back into the Synology and issued "Back Up Now" for all backup tasks. I had expected the version count to be reset to 1, but instead it retained the version count. Uneasy with this obvious difference between Time Backup and the content of the hard disk I resorted to deleting and re-creating all backup tasks. This seems to have done it.

Update 2013-12-13: The file system has run out of inodes again. Seems like you should use an above standard ratio of inodes to size for Time Backup.

1 comment:

  1. Thank you for your blogpost, it gave me an idea how I could solve my backup failure!