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

add a pass through mode for large files #4

Open
msmeissn opened this issue Apr 19, 2017 · 8 comments
Open

add a pass through mode for large files #4

msmeissn opened this issue Apr 19, 2017 · 8 comments

Comments

@msmeissn
Copy link
Contributor

via an IRC reporter

huge files will cause huge memory usage, as the file is cached in meory.

Investigate how fuse does pass through file reading and implement that

@msmeissn
Copy link
Contributor Author

I am adding gp_camera_file_read there

@pmnordkvist
Copy link

I do extensive backups on several different devices and have experience big problems with large files over gphotofs which forced me to use gphoto2 directly to copy files over a few hundred megabytes so this is very helpful.

One thing I have read in the past but can't seem to find is information on where gphotofs stores temporary files? Is that in TMPDIR? I run OS on a fast partition and copy to a slow one and would like to store temporary files on the remote partition if possible.

@msmeissn msmeissn reopened this Apr 29, 2017
@msmeissn
Copy link
Contributor Author

currently gphotofs stores it only in memory, without using temporary backing storage.

what i am adding currently is pass through, so it does not need to be stored in memory.

msmeissn added a commit that referenced this issue Apr 30, 2017
@michael-berlin
Copy link

I think this is fixed?

I've successfully used the current code from the master branch to copy large files (> 2GB) from an iPhone. That was on a Raspberry Pi with only 1 GB RAM. The Fuse process gphotofs never went over ~10 MB memory usage during that time.

@msmeissn
Copy link
Contributor Author

msmeissn commented Sep 6, 2017

reading is fixed, so yes

writing still uses in-memory state, have to do that still.

@robertalers
Copy link

When i take a picture with my Nikon d750 new files does nog automaticly show up in the mounted directory . Log states it should from 1.0 upward.
Is this a bug or is there something i’m doing wrong?

@msmeissn
Copy link
Contributor Author

msmeissn commented Nov 7, 2017

hmm, we are polling events so we should get notifications for new files and add them

@robertalers
Copy link

I use a RPI, could this cause the problem? Any actions I can take te debug this? Thank you for your response!

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

4 participants