-
Notifications
You must be signed in to change notification settings - Fork 244
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
gcfs: unable to access mount: No such file or directory #275
Comments
I used "-fusedebug" and got this output: Nov 25 03:48:01 spin8 gocryptfs[6472]: go-fuse: Dispatch 2: GETATTR, NodeId: 1. data: {Fh 0} I also used strace on "ls dump" but I cannot find any relevant errors there: execve("/bin/ls", ["ls", "dump"], [/* 26 vars /]) = 0 |
Hi! Can you run
an post the output? Note: You need gocryptfs 1.6 for |
Hello, thanks for your response, I did: gocryptfs -fsck gdrive/safe Could this happen because I accessed the gocryptfs folder from different servers? kind regards |
I think the gocryptfs.diriv file is missing. You can check by looking into the encrypted folder, it should be next to gocryptfs.conf. This file is created on "gocryptfs -init" and never modified again, so I'm not sure how that can happen. |
PS: if you look at syslog (journalctl -f), you will probably see a message related to the missing file. |
I see the two files in the encrypted folder, they havent been touched since creation: 1 -rwxr-xr-x 2 root root 384 Nov 18 22:48 gocryptfs.conf How to access the crypted data again? Is there any way? :) thanks alot for your assistance |
I just noticed that the "gocryptfs.diriv.19" file is named just "gocryptfs.diriv" in a fresh setup. I renamed it and the mount is working again! I dont know how it got renamed, maybe a bug? Thanks for your hints so far! :) 🥇 edit: after some testing with a fresh setup, there is again this renaming failure - also in all subdirectories. I use precompiled version 1.6 and will now try to compile myself and see if the problems persist. edit2: on my local box I cannot reproduce the problem, only via GCSF(google drive) - I guess it could have to do with the way googledrive/GCSF works - the diriv is not accessible blockwise, it needs to get downloaded and uploaded - maybe thats why the file has an attached number - I only know that from existing files |
Does it always get the ".19" extension? |
no, some subfolder IV's got .12 and other numbers. I posted the issue on GCSF in hope for help there, it doesnt seem to be related to gocryptfs! :-) |
solution one: is it somehow possible to use one global diriv for all (sub)folders? both would solve the problem (workaround) thanks in advance for your help mate! |
So the idea I had what could be causing the problem for gcfs is that the diriv file is created as UNWRITABLE from the start. This seems confusing, but when a file is first created, you can create it without write permissions but still write to it, and this is what gocryptfs does to protect the diriv files from modification. The test is simple:
But this seems to work OK on gcfs and I don't get a .number postfix:
|
hi,
after pushing some data in and umounting, i am now unable to access (again)mounted cipher dir:
gocryptfs googledrive/safe dump
Password:
Decrypting master key
Filesystem mounted and ready.
ls dump/
ls: cannot open directory 'dump/': No such file or directory
I had it before and thought it was a bug from an older version, then updated to the latest release from here. But now the same problem. When creating a new cipherdir, everything works. I also found no debug option to find out more info on whats going wrong - please help me to give you more infos :)
kind regards,
plati
The text was updated successfully, but these errors were encountered: