Backup using rsync encrypted gives "ENAMETOOLONG" error.
-
Hello,
It seems when using encryption and rsync for backing up Cloudron (this particular configuration is new to my environment), I get an error message with "ENAMETOOLONG", suggesting the file path or name of the file is too long.
The exact error in my case is as follows:
ENAMETOOLONG: name too long, open '/cloudron-backups/snapshot/app_6b96bd5a-0f84-43aa-8558-7544ec25b19e/36gHI-IuCvvayKXxGPRB1Q/ounM2diChi8DjI1Q3dzMDQ/gGJEz0QgDgsR3jo4XlgYXA/lqAVjQcV8mH8VRRpjjOr1g/kJEwyjEtwqB7Sx2f6L-GUw/fu1zv6VH8LxelOLxe0ub0bgswf82VC21bSpaTxbYSq8fHBlOMRamME-qppekZ+OAzSVbZVxrDKhuYkwdDOLWxWGnFX3QZMFdo0l1mjw54vs-piviwM4PIThP9VIlXwl8ngYif83b3MCNO5lyxmQedqOPbjeVBsJOCzttwAqHl04ys1iTlQIrQMY1d2+adF15nNzZONfL4l-Y8S6TnwAySPkhvBLZY8khSMjI6KcZ-8SO8y1ML-NIM3uyj3MtKVsW
How can this type of event be worked around / resolved? In other words, since the filenames are encrypted too I'm not sure which file this references so I don't think I can even try to work around it by editing the file name before it's encrypted. And if it only too long because of it's encrypted value, versus if it wasn't encrypted? If so, I wonder if the encryption can be improved to avoid lengthy file names?
This of course works fine with encrypted tgz method, just not encrypted rsync.
Any help would be appreciated.
-
Update: I can confirm this is only an issue with encrypted rsync. It works fine with encrypted tgz. And if I use non-encrypted rsync, I actually get a different issue all together where it fails to remove a directory for some reason (I may make a different post about that because I'd ultimately preferred to use rsync since I have a large amount of data, and my understanding is rsync backups would be much quicker after the initial one, but please correct me if I'm wrong).
Edit: Created new post for the non-encrypted rsync issue: Backup issue in rsync non-encrypted filesystem type. Never moves past status of removing directory for one particular app (Rainloop).
2 -
@d19dotca Yes, this is in a known limitation with Cloudron's rsync backup in general. Please see the caveat in https://cloudron.io/documentation/backups/#rsync-format (the last one). I will make it a warning so that it stands out a bit more. It's possible to fix but it requires some work.
-
@d19dotca Yes, this is in a known limitation with Cloudron's rsync backup in general. Please see the caveat in https://cloudron.io/documentation/backups/#rsync-format (the last one). I will make it a warning so that it stands out a bit more. It's possible to fix but it requires some work.
-
@d19dotca I think if you make the backups unencrypted, it should work (as long as the filesystem can handle file lengths the same as your main file system). I have opened https://git.cloudron.io/cloudron/box/issues/670 to track this encrypted bug. Let's see if there is a bug in the non-encrypted one in the other thread.
-
@d19dotca I think if you make the backups unencrypted, it should work (as long as the filesystem can handle file lengths the same as your main file system). I have opened https://git.cloudron.io/cloudron/box/issues/670 to track this encrypted bug. Let's see if there is a bug in the non-encrypted one in the other thread.
@girish Unfortunately I have a different issue when running non-encrypted, which is posted here: https://forum.cloudron.io/topic/2270/backup-issue-in-rsync-non-encrypted-filesystem-type-never-moves-past-status-of-removing-directory-for-one-particular-app
