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

New files or changes in a shared location are not visible in finder to users without upspinfs restart #593

Open
sevan opened this issue Jun 23, 2018 · 5 comments

Comments

@sevan
Copy link

sevan commented Jun 23, 2018

I have a directory which I share with several people so we can exchange data with each other. Everyone I'm sharing with is a macOS user & accesses the shared space using the integration with finder via FUSE & upspinfs. The problem is that once a new file is copied to my shared directory by someone else, the file appears briefly in finder for that person after the copy has completed and then it disappears. Once they restart upspinfs, the file is actually visible correctly for them.
For other people, propagation is hit and miss, some see the changes/additions when they complete others do not, until upspinfs has restarted.
Everyone is able to see files correctly at all times if they access things using upspin instead.
The question is, is this an issue with upspinfs or FUSE on OS X? Any pointers appreciated.

@sevan sevan changed the title New files or changes in a shared locat are not visible in finder to users without upspinfs restart New files or changes in a shared location are not visible in finder to users without upspinfs restart Jun 23, 2018
@otremblay
Copy link

In my case for my upspin mount to show up at all in Finder I had to make it compile as a network drive.

@sevan
Copy link
Author

sevan commented Jun 29, 2018

Can you explain what you mean by "I had to make it compile as a network drive'?
I just use the stock binaries published on upspin.io and use https://github.com/upspin/upspin/blob/master/cmd/upspinfs/scripts/mount_darwin script.

@otremblay
Copy link

otremblay commented Jun 29, 2018 via email

@sevan
Copy link
Author

sevan commented Jun 29, 2018

Thanks for the pointer, I'll give a try next week to see how it works out.

@sevan
Copy link
Author

sevan commented Sep 11, 2018

Not treating the mount as a localvolume doesn't make any difference.
I tried playing with NoAppleXattr and NoAppleDouble.
Extended attributes are definitely needed. When mounting with NoAppleXattr, I'm unable to write to my own shared space.
Fuse on macOS supports more options than Bazel/Fuse currently supports the nolocalcaches mount option sounds interesting

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

2 participants