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.

Sign up for GitHub

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

Jump to bottom

ListObjects and writeMessage errors #101

Closed
jacobsa opened this issue Aug 3, 2015 · 3 comments
Closed

ListObjects and writeMessage errors #101

jacobsa opened this issue Aug 3, 2015 · 3 comments

Comments

@jacobsa
Copy link
Contributor

jacobsa commented Aug 3, 2015

A couple of users (including @kernelt in #95) have reported errors that look like this:

fuse: 2015/08/04 07:55:31.358121 *fuseops.ReadDirOp error: readAllEntries: ReadEntries: ListObjects: EOF
fuse: 2015/08/04 07:55:31.358148 writeMessage: invalid argument

I can semi-reliably reproduce this now. It seems there are two bugs, that should be tackled in this order:

  1. The error from ReadDirOp is apparently mishandled by writeMessage.
  2. ReadDirOp gets the error in the first place.
@jacobsa jacobsa mentioned this issue Aug 3, 2015
Closed
jacobsa added a commit to jacobsa/fuse that referenced this issue Aug 3, 2015
@jacobsa
Added a test that reproduces GoogleCloudPlatform/gcsfuse#101.
8947980
jacobsa added a commit to jacobsa/fuse that referenced this issue Aug 3, 2015
@jacobsa
Added a test for various file system error conditions.
589f6c3 
This reproduces the writeMessage errors from
GoogleCloudPlatform/gcsfuse#101.
jacobsa added a commit to jacobsa/fuse that referenced this issue Aug 4, 2015
@jacobsa
Fixed two issues with error responses to the kernel.
b5c1fd6 
One of them caused the writeMessage error observed on OS X in
GoogleCloudPlatform/gcsfuse#101.
jacobsa added a commit that referenced this issue Aug 4, 2015
@jacobsa
Updated jacobsa/fuse to b5c1fd6.
fbda894 
This fixes the writeMessage errors seen in #101.
@jacobsa
Copy link
Contributor Author

jacobsa commented Aug 4, 2015

It seems I can reproduce these errors with golang/go@a3ffd83, but not with golang/go@b3bf38e. I wonder if there was an HTTP bug fixed between those two commits...

@jacobsa
Copy link
Contributor Author

jacobsa commented Aug 4, 2015

Okay yeah, the EOF bug was introduced by golang/go@0cf48b4 and was fixed by golang/go@7e70c24.

I've confirmed by building with an old version of Go that commit fbda894 fixes the writeMessage issue. So all that remains is to make a new release built with a fixed version of Go.

@jacobsa
Copy link
Contributor Author

jacobsa commented Aug 4, 2015

Fixed with v0.6.0.

@jacobsa jacobsa closed this as completed Aug 4, 2015
jacobsa added a commit that referenced this issue Aug 4, 2015
@jacobsa
Updated jacobsa/fuse to b5c1fd6.
ec2d18c 
This fixes the writeMessage errors seen in #101.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jacobsa