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

"Not enough free space" errors from Finder on OS X #125

Closed
jacobsa opened this issue Sep 5, 2015 · 2 comments
Closed

"Not enough free space" errors from Finder on OS X #125

jacobsa opened this issue Sep 5, 2015 · 2 comments

Comments

@jacobsa
Copy link
Contributor

jacobsa commented Sep 5, 2015

Attempting to copy a file into a gcsfuse mount from the Finder results in free space errors; see this question. This probably has to do with returning a zero response to statfs questions.

Make sure gcsfuse plays nicely with Finder and Cocoa applications.

jacobsa added a commit that referenced this issue Sep 8, 2015
@jacobsa
Copy link
Contributor Author

jacobsa commented Sep 8, 2015

Notes:

  • Setting block size to 2^12 and total/free/available number of blocks to 2^38 works, and the Finder is able to report the sizes.
  • It still chokes on attempting to set mode after writing, however.
  • It also shows a crappy volumne name ("OSXFUSE" or similar).

So:

  • Update the fuse package to allow handling a statfs op. In fact, note that the user must handle this on OS X for the mount to succeed. Add an integration test using memfs.
  • In gcsfuse, set the values as above. Make sure on both OS X and Linux that the actual read and write sizes sent by the kernel do not change.
  • Tackle the mode problem. Probably just ignore it instead of returning ENOSYS (sigh). Make sure to update the semantics documentation on this point.
  • Tackle the volume name problem, using the volname option.
  • Also try saving from a Cocoa app.
  • Make a release.

jacobsa added a commit to jacobsa/fuse that referenced this issue Sep 9, 2015
File systems must now handle StatFSOp in order to mount correctly on
OS X.

For GoogleCloudPlatform/gcsfuse#125.
jacobsa added a commit to jacobsa/fuse that referenced this issue Sep 9, 2015
While I was at it, added tests for fsname. I can't figure out how to
test the volume name.

For GoogleCloudPlatform/gcsfuse#125.
jacobsa added a commit to jacobsa/fuse that referenced this issue Sep 10, 2015
On OS X we can't set block size above 2^17, but we want to encourage
users to send large reads and writes.

For GoogleCloudPlatform/gcsfuse#125.
jacobsa added a commit that referenced this issue Sep 10, 2015
This causes the Finder to stop refusing to write to the file system.

For #125.
jacobsa added a commit that referenced this issue Sep 10, 2015
Currently the semantics are underspecified, and we actually return
ENOSYS in this case. But we need to silently ignore changes instead,
since otherwise the OS X Finder gives the user an error when they
attempt to copy in a file or directory (issue #125). I have observed
similar non-fatal errors printed on some Linux distributions.
jacobsa added a commit that referenced this issue Sep 10, 2015
@jacobsa
Copy link
Contributor Author

jacobsa commented Sep 10, 2015

Still to do: Update the installation instructions (to say brew install gcsfuse again) and the ServerFault answer once homebrew/homebrew-fuse#15 is pulled.

jacobsa added a commit that referenced this issue Sep 10, 2015
Now that Homebrew/homebrew-fuse@211eb24 is in.

This reverts commit 8ec5655.

For #125.
@jacobsa jacobsa closed this as completed Sep 10, 2015
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

1 participant