sukria/Backup-Manager — Issue #18: Too many levels of symbolic links
Author: Glandos
Created: 2012-01-24 09:44:42+00:00
State: open

When BM_ARCHIVE_PURGEDUPS is set to true, a symlink is created from the old file to the new one. However, when a configuration file didn't change for 8 days, the symlink limit is reached, and old file can't be accessed by name.

I got no obvious solution for that.

If symlinks are created from the new file to the old file, then we'll get in trouble when the real purge comes.
It is maybe possible to go backward in previous symlinks and fix them when creating a new one, but then the script could get really complex.
Finally, the use of hardlinks could change this. However, I'm nearly sure there's also a limitations on the number of hardlinks an inode can have.