You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We had borgmatic set up on one of our Synologies, but I can't remember which method we set it up with. Long story short, Synology only provides VERY little space on /. Borg was running fine for months, but its cache was being written to /root/.borg (Or something like that) and so, a time came when / had no space available, so Synology stopped functioning correctly. We had to SSH in to figure out what was going on and to remove the cache. I haven't had a chance to reinvestigate yet, but if the setup instructions are indeed allowing Borg to write to /, they should be adjusted to cause Borg to write its cache to the shared folder location.
The text was updated successfully, but these errors were encountered:
Yeah I can totally write up something later this week. Just to clarify - You only do this symlinking on Synology devices, right? On a standard linux machine, this isn't necessary, right?
Yes, only on Syno because if you run the backup as root user, there is limited space in /root. So I link it to /volumexx/homes/root or something instead. It could be that /volume/homes/root gets copied during updates, but I'm not sure.
We had borgmatic set up on one of our Synologies, but I can't remember which method we set it up with. Long story short, Synology only provides VERY little space on /. Borg was running fine for months, but its cache was being written to /root/.borg (Or something like that) and so, a time came when / had no space available, so Synology stopped functioning correctly. We had to SSH in to figure out what was going on and to remove the cache. I haven't had a chance to reinvestigate yet, but if the setup instructions are indeed allowing Borg to write to /, they should be adjusted to cause Borg to write its cache to the shared folder location.
The text was updated successfully, but these errors were encountered: