-
Notifications
You must be signed in to change notification settings - Fork 90
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
gocryptfs / securefs support #45
Comments
i noticed the following: the files are NOT RENAMED, it just seems so. when using "rclone" I see all files correct, also the modification didnt change - which it should when rename occurs. So I guess GCSF has problems with files which have the same filename (but sit in other folder) - please check - GCSF is the fastest but I cannot use it currently because of this bug thanks in advance |
after some research I found the lines 372-374 in file_manager.rs and commented them out, now its working - seems the code did this on purpose. I cannot see any errors yet, also the identical files have different content - why is this suffix needed? |
Late update: after @platinum55's change (integrated in 0.1.23) you can now disable the behavior which renamed identical files. The reason behind this was a mismatch between Google Drive -- which allows files with identical names to be placed in the same directory -- and traditional file systems -- which do not. Without adding a distinctive feature such as an indexed suffix to each identical file, users would not be able to do anything with N-1 out of N such files. For instance, imagine 100 files named Indexing the file names partially solves this problem, but it also creates others as you have noticed first-hand. Therefore try setting |
Hello,
I had problems with gocryptfs, the diriv files got renamed(attached number, maybe while gocryptfs tried to edit the file) and also with securefs, which is not usable at all with GCSF
Maybe there is a special GCSF config needed? Please help :)
The problem with gocryptfs is described here:
rfjakob/gocryptfs#275
kind regards
The text was updated successfully, but these errors were encountered: