Crashplan doesn't see folders/files with non-US accents (PART 2)
#12 Updated by Anonymous almost 6 years ago
Please read the attached #3550 ticket history (PDF).
For some reason, simply editing the locale doesn`t works... Crashplan still believes his locale is "C", instead of UTF-8 (be it en_US.UTF-8 or pt_BR.UTF-8) .
Manually setting the correct locale parameters fixes typing and reading in the shell context, but:
1. In next jail restart, the "C" comes back.
2. Crashplan service completely ignores it, as I mentioned in #3550 and above.
For some reason, I believe that fixing the ".1" issue above (correct locale in jail start) will fix the whole problem, because it's possible that Crashplan service tries to find the "original" locale that comes in when the jail starts (maybe a config file of the jail?)
It's a easy problem to reproduce, and a big problem to non-US Crashplan FreeNAS users.
By killing Linux Jails, you will force us (non-US) to choose between:
- Don't upgrade to 9.3 until this ticket is fixed
- Upgrade but don't backup files that has accented chars
Both options are equally terrible
Please take a loot at it.
#13 Updated by Anonymous over 5 years ago
- Erased my Linux jail
- Migrated everything to ZFS
- Upgraded to 9.3
- Installed the official Crashplan plugin in a plugin jail
- Configured everything just right
But the problem still remains: no files with non-US accented chars are uploaded/recognized by Crashplan.
#14 Updated by Mike L about 5 years ago
Also seconding that an official fix for this would be quite helpful. Realizing that half your remote backup strategy is now useless is not a good feeling.
This source indicates that an update to the linux compatibility layer is what is needed.
I can second that that does seem to work for my install.