Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Synology: Does the suggested setup store the borg cache in /root? #11

Open
techdaddies-kevin opened this issue Nov 11, 2021 · 3 comments

Comments

@techdaddies-kevin
Copy link

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.

@m3nu
Copy link
Collaborator

m3nu commented Nov 11, 2021

This is true. I usually symlink the .cache folder to the main data folder due to that. If you have many files, this is a must.

Wanna do a PR to document this?

@techdaddies-kevin
Copy link
Author

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?

@m3nu
Copy link
Collaborator

m3nu commented Nov 12, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants