-
Notifications
You must be signed in to change notification settings - Fork 21
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
encfs is unable to write file contents to the mounted Google Drive directory #44
Comments
The one thing that is odd is that these commands do not work for you: I can't reproduce the failure. Can you rerun those commands only and send the log associated with it? |
I'll post the logs at the end of this post. First, though, I want to make sure there's no confusion. Those second and third commands (the echo commands) only fail when I try them inside the encfs which is mounted from a Google Drive directory. They work if I try them on the local filesystem, an encfs which is mounted from a local directory, or directly inside the Google Drive mount. I've tried these commands on two machines and had the same trouble (one running openSuSE 13.1 x64, the other Debian sid x64), so hopefully it's not just a foolish configuration error on my part. Hopefully that's clear. Now, for these logs what I've done is made a new, empty directory in my Google Drive (called bugtest). Then I used encfs to create an encfs inside that directory, and mounted that encfs in ~/mnt. So, step by step, here's what I did:
In contrast, if I run these commands directly inside /tmp/mnt, where the Google Drive is mounted, it works:
Interestingly, ecryptfs fails similarly to how encfs fails (or I'd just use that instead):
Here's the log from the coffee script (I changed the settings file so it debugged to stdout) when making the encfs and doing the mkdir / touch commands:
Here's the output from encfs running in debug mode:
|
I've played with this a little bit since I made the report. It looks like what's happening is that encfs tries to open files in r+w mode when we do the echo command, and this doesn't seem to be supported at the moment? The code from the coffee script that gets run on a r+w open just always returns ENOENT:
Note that the "tried to open [...]" log doesn't show up in the output I pasted before, since that line is commented out in the repo. |
I haven't had much time to work on GDrive. Thanks for digging down and finding the cause. |
Transmission Torrent Client also attempts to open files in r+w mode, causing the script to crash! Is there any progress on this? :) |
im also trying to use encfs and this r+w mode not being supported is disappointing :( |
Would it take much to support it? Is it much different that read or write? |
I'd like to have an encrypted directory in my Google Drive (via encfs), but I think there's some compatibility issue in conjunction with node-gdrive-fuse.
I've got my Google Drive mounted (via node-gdrive-fuse) at /tmp/mnt.
And I've done a
mkdir /tmp/mnt/test
.And a mkdir
~/mnt
.Then I do an
encfs /tmp/mnt ~/mnt
.That all works fine. The problem is that any attempt to write content to any files in
~/mnt
fails. I can create empty files (usingtouch
) or directories (usingmkdir
), but nothing else works.For example,
touch test
works and creates an empty file called test. Butecho test > test
doesn't work. It errors withbash: test: No such file or directory
, producing just an empty file.encfs does seem to be able to read files, though. I did an experiment where I created an encfs locally, and then copied that directory over to /tmp/mnt. I then mounted that encfs, and I was able to
cat
the contents of the files.I'm posting the contents of the node-gdrive-fuse log, and the debug output from encfs, below. For the test that produced these logs, I mounted a new encfs in
~/mnt
and then issued just three commands:touch test
echo test > test
(fails -- file already exists)echo test > test2
(fails -- errors as above)GDriveF4JS.log
encfs log
The text was updated successfully, but these errors were encountered: