-
Notifications
You must be signed in to change notification settings - Fork 96
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
Error reading files larger than 512KB #81
Comments
Can reproduce with 0.13.14, tried copying a file with 'dd', and I'm getting only the first 524KiB (which is 512KB) output of gdfs -d:
Every read operation works until the 512KB limit, then there's an error -5 and dd gives up. |
I've been able to reproduce the issue with versions 0.13.13, 0.13.12, 0.13.10, 0.13.9, 0.13.8, 0.13.5, and 0.13.4, and then I've given up testing. At this point, I'm thinking something's wrong with one of the dependencies of gdrivefs, or Google changed their API... |
I was working under the same assumption, so i tried to upgrade the google-api thing, but that didn't do diddly squat :( |
After a bit of fiddling, and getting it to output debugging logging instead of just warning logging, i've gotten a bit more information out of it. (A LOT more infact) I removed the huge chunk of data that fuse dumped, everything else is as is output to the log: |
@dsoprea i tried clearing out the tmp directory between each test, in the hopes the log would show something different, but it was the same. Worst part, i suck at python, so i can't even understand half of it /o\ |
Thanks for getting the ball rolling on this. I'll have to look into it. I don't think I've ever had this problem (I've downloaded files larger than that). Neither of you happen to have experience with Google's OAuth 2.0 Playground, do you? There's a script called tools/gdfsdumpentry, which will allow us to see exactly what information Google is returning for that file/entry. Unfortunately, that script isn't pushed into the executable path, and, because of the way the package was configured, that file will therefore not be included when installing from pip. I'd fix that, right now, except that I'd be unable to test it (I'm currently on a Mac). If you're using a clone of the project, you'll have that script, though. It should work. We could definitely get some direction if you can run it with a problematic file, and paste the output. |
@dsoprea sadly i don't, i've tried running gdfsdumpentry however, but not entirely sure on the way to tell it to do something. So far i've tried |
Try adding a prefixing slash, or the whole relative path if it's not in the
|
Here we go..
Data dumped
|
Assuming that 9333398 is the correct size, it definitely looks like a Dustin On Sun, Jul 6, 2014 at 3:00 PM, Michael Karbowiak [email protected]
|
File is indeed |
I believe you. I'll let you know when I have something. On Sun, Jul 6, 2014 at 3:08 PM, Michael Karbowiak [email protected]
|
Awesome, thanks for taking a look at it :) |
Happy to help. On Sun, Jul 6, 2014 at 3:11 PM, Michael Karbowiak [email protected]
|
This is a complete shot in the dark, but from my googling online I've seen that to upload files to GDrive using the API, you need to send it in 512KB chunks - could it be that they've changed the download endpoints to also work in 512KB chunks? For uniformity? (And also perhaps to keep their response handling times low) I'm pretty sure the GDrive sync desktop client (for Windows) is able to work in 512KB chunks for both download & upload - then again it isn't the most stable thing in the world, and they may be using private/undocumented APIs. |
Any headway on this? :) |
Sorry, no. I'll try to work on this, this weekend. On Thu, Jul 10, 2014 at 1:17 PM, Michael Karbowiak <[email protected]
|
I completely forgot to check in, and when i remembered it, i were all kinds of happy "YAY IT'LL WORK".. |
Son of a gun. Okay... I'm working on it, today. On Sun, Jul 20, 2014 at 11:40 AM, Michael Karbowiak <
|
Any news on this? Would it speed up solving this issue if I donate you $ 50? I don't want to hijack this issue, but I don't want to open a new issue for this. Files containing an umlaut/a special character (üäöß) in their name can't be read. |
I'm spread thin. However, the more people that indicate they're The unicode problem that you're experiencing probably relates to something On Wed, Jul 23, 2014 at 1:54 AM, flow [email protected] wrote:
|
Ok. To be fair to you, there are even more people waiting to get this resolved. You can find our intention here: https://forums.plex.tv/index.php/topic/113159-an-alternative-to-bitcasa-google-drive-for-work/ |
I read the thread. My bad. I'll get it done ASAP. @karbowiak That's been a favorite clip (Jim Carrey on Letterman) of mine Dustin On Wed, Jul 23, 2014 at 2:19 PM, flow [email protected] wrote:
|
@dsoprea haha, i was looking for an image to convey my happiness, and it fit perfectly - but now that i've seen the actual footage, it's just that much better ! Do let me/us know if you need testing done, i'll be more than happy to ruin some data to help the cause :) |
I also would love to contribute my logs to this issue. Currently this is an issue with most programs that mount Google Drive to include: NetDrive So far ExpanDrive is the only mount program I've found that can get around the streaming issue. Sadly it only works for Mac and Windows. I would love to see GDriveFS be able to blow past this limitation! |
I desperately want to work on this for you guys, but I just lack Dustin On Fri, Aug 8, 2014 at 8:55 PM, Zed [email protected] wrote:
|
Of course! Don't let anyone tell you different :P |
I, too, am having the same issue. However, I am not a programmer, nor do I play one on TV. I will be patiently waiting. Just remember your legions of fans that are awaiting your magic. Thank you for all the hard work! |
Hey man! How's it going with your corporate map-reduce project? :) |
The corporate use-cases gave me a practical reason to commission it within Dustin On Wed, Aug 27, 2014 at 6:20 AM, Michael Karbowiak <[email protected]
|
Hello, would just like to ask if you have had time to check this problem out, or if anyone found a workaround to this problem? |
Yes
Yes.
All that I have seen. I am now getting "Input/output error" when I try to copy files from my gdrive. |
Running into the same issue here as well |
Any updated on this issue @dsoprea ? :) If wanted, i'm sure we can pile some money into it via bountysource. |
Sorry for not being as responsive as I should be. I love this project, and there are so many people that are now supporting it that I need to get back on it. I'll be working on this issue, specifically, tomorrow. Thanks for your patience. I appreciate it more than you know. |
@karbowiak Alright. I relent. I've placed a donation icon at the top of the documentation. |
@dsoprea awesome, i look forward to reading from GDrive! <3 I'll make sure to send a few bucks your way once my credit card arrives. Managed to get it stolen last week while shopping /o\ |
@dsoprea I received the following error when attempting to donate:
|
@dsoprea I just received the same message that @rxsegrxup received..
|
It's Paypal. They flagged me as a potential terrorist, and at least four of the verification methods are broken. I had to switch accounts. Should be fine, now. |
@dsoprea as a potential terrorist? lol.. Fucking Paypal |
Thank you for your donation and support, Michael. |
No problems @dsoprea - i would've donated more, but christmas is right around the corner, i shall revisit the donate link once December rolls around :) |
When I first read @dsoprea's comment I thought to myself "Your welcome but I didn't donate yet" LOL completely forgetting how common the name "Michael" is. I know a guy that works for paypal. I'll definitely be asking hom about this lol |
Thank you for your donation and support, @rxsegrxup. |
I was taken away from this for a couple of days, but I'm currently rebuilding the way that we manage open-files. I have a feeling that the size problem was a consequence of this. |
This problem is likely fixed (in the "development" branch). There are a couple of remaining issues that keep me from merging it, but it's very close. I'd say that I'd try to get it done this week, but Thanksgiving is going to interfere. |
@dsoprea any chance you could provide a high-level explanation of those bugs? |
There are some anomalies with how we process the change-events that we subscribe to from GD. I have to debug why change-processing interferes with normal operations that are happening concurrently. I generally debug with this turned-off, to make it easier to control what's going on. But, when I reenabled this after making the other changes, somethings happening in the change-thread that's interrupting the file-upload. The other issue has to do with the vim editor not opening saving files correctly. I often use vim to validate the current design because it has such an immensely complicated file-usage pattern... It opens, closes, modifies, and unlinks so many files when it's opening and closing files that it's impossible for a general usage bug to sneak by. For some reason none of its operations fail, but the file that was created is created empty. This needs to be investigated. |
This should be fixed in this release: https://github.com/dsoprea/GDriveFS/releases/tag/0.14.0 Please confirm. |
Can someone confirm the fix? |
Just done a quick test. When I copy a jpg out it looks the right size but is reported to be corrupted. How can I check what version I'm running? |
Sorry. I didn't see this.
|
Please keep in contact. I did a check and my hashes agree. |
Yes it looks like I am using 0.14.2: $ pip2 freeze | grep gdrivefs Warning: cannot find svn location for $ pip2 search gdrivefs gdrivefs - A complete FUSE adapter for Google $ python2 Python 2.7.9 (default, Dec 11 2014, 04:42:00) [GCC 4.9.2] on
|
I also get this problem
|
Hi.
I'm having an issue where uploading files larger than 512KB works great, but reading them back fails.
I can get the first 512KB of the file, and then it just errors out.
Below 512KB and it works great however.
Error logs:
gdrivefs with debug
gdrivefs.log
Tried using the latest version from pip, and that was released, only thing i havn't tried is using the source repo, but i assume 0.13.14 is latest from the source repo.
The text was updated successfully, but these errors were encountered: