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

gocryptfs / securefs support #45

Closed
platinum55 opened this issue Nov 26, 2018 · 3 comments
Closed

gocryptfs / securefs support #45

platinum55 opened this issue Nov 26, 2018 · 3 comments

Comments

@platinum55
Copy link
Contributor

platinum55 commented Nov 26, 2018

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

@platinum55
Copy link
Contributor Author

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

@platinum55
Copy link
Contributor Author

platinum55 commented Dec 4, 2018

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?

@harababurel
Copy link
Owner

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 foo.txt, each containing something different. cat foo.txt has no way of knowing which one the user is referring to, so it would output the contents of whatever file GCSF decided is matched to that particular name, leaving all other 99 inaccessible.

Indexing the file names partially solves this problem, but it also creates others as you have noticed first-hand. Therefore try setting rename_identical_files = false in your config.

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