amarder
(Andrew Marder)
November 8, 2024, 2:20pm
1
I'm using an NFS mount on macOS with a local
type remote. I think it's working but I see the following error message in the terminal:
ERROR : nfs: failing create to indicate lack of support for 'exclusive' mode.
Can I safely ignore this error message?
Background Info
$ rclone version
rclone v1.68.1
- os/version: darwin 15.1 (64 bit)
- os/kernel: 24.1.0 (arm64)
- os/type: darwin
- os/arch: arm64 (ARMv8 compatible)
- go/version: go1.23.1
- go/linking: dynamic
- go/tags: none
I am not using a cloud storage system, I'm using Local Disk for my remote.
Here's the command I'm running:
rclone nfsmount --vfs-cache-mode full localcrypt:/path/to/files /path/to/local/mount
Here's my config:
[local]
type = local
[localcrypt]
type = crypt
remote = local:/path/to/folder
password = XXX
password2 = XXX
An example log can be viewed here: rclone.log · GitHub
Thanks for the help, rclone rocks!
Andrew
nfsmount on macOS is work in progress. There are still some issues to be fixed, e.g. Microsoft Office apps can't write on an S3 mount when mounted with nfsmount on MacOS 14.5 · Issue #7973 · rclone/rclone · GitHub
I prefer still rclone mount
and FUSE-T. It is kext-less and uses NFS as well.
If nfsmount
works for you - and you do not have any issues then you can ignore any warnings and errors. But no guarantees what results will be:)
1 Like
amarder
(Andrew Marder)
November 8, 2024, 2:51pm
3
Thank you, this is super helpful! I'm going to switch over to FUSE-T...
You can even install FUSE-T without root:) There is "how to" in the below issue discussion:
opened 05:02PM - 21 Aug 24 UTC
closed 06:09AM - 28 Aug 24 UTC
bug
serve nfs
#### What is the problem you are having with rclone?
The nfsmount command doe… sn't work properly in version 1.68.0 of rclone. It mounts the remote but, in the Finder, shows certain subfolders and as having "no entry" icons. Those subfolders cannot be accessed. Also, some files are unable to be accessed.
The mount itself seems to work, but items within the mount are unaccessible, even if I have full permissions on the remote.
Trying to list these subfolders from the command line gives the following error:
```
ls: ./ERP: Stale NFS file handle
```
When trying to access these items from Mac Finder, a popup occurs with the following message: `The folder “ERP” can’t be opened because you don’t have permission to see its contents.`
When using version 1.67.0, on the exact same remote, with the exact same authentication options, there are none of these issues.
#### What is your rclone version (output from `rclone version`)
1.68.0
#### Which OS you are using and how many bits (e.g. Windows 7, 64 bit)
MacOS Sonoma 14.6.1
#### Which cloud storage system are you using? (e.g. Google Drive)
Reproduced with AWS S3 and Pcloud type remotes.
#### The command you were trying to run (e.g. `rclone copy /tmp remote:tmp`)
rclone --vfs-cache-mode writes --cache-dir ./cache nfsmount aws: ./mount1 --allow-other --default-permissions
#### A log from the command with the `-vv` flag (e.g. output from `rclone -vv copy /tmp remote:tmp`)
2024/08/21 10:00:54 DEBUG : [NFS DEBUG] request: RPC #1628752891 (nfs.GetAttr)
2024/08/21 10:00:54 DEBUG : nfs: FromHandle: handle=D90872F95AB048679EB4CF0444C8F98B
2024/08/21 10:00:54 DEBUG : nfs: >FromHandle: path=[], err=<nil>
2024/08/21 10:00:54 DEBUG : : Lstat:
2024/08/21 10:00:54 DEBUG : : >Lstat: fi=/, err=<nil>
2024/08/21 10:00:54 DEBUG : [NFS DEBUG] request: RPC #1628752892 (nfs.Access)
2024/08/21 10:00:54 DEBUG : nfs: FromHandle: handle=0F83C09216C342ED92C1516F387EB179
2024/08/21 10:00:54 DEBUG : nfs: >FromHandle: path=[], err=Invalid file handle
2024/08/21 10:00:54 DEBUG : [NFS DEBUG] request: RPC #1628752893 (nfs.Access)
2024/08/21 10:00:54 DEBUG : nfs: FromHandle: handle=0F83C09216C342ED92C1516F387EB179
2024/08/21 10:00:54 DEBUG : nfs: >FromHandle: path=[], err=Invalid file handle
2024/08/21 10:00:54 DEBUG : [NFS DEBUG] request: RPC #1628752894 (nfs.Access)
2024/08/21 10:00:54 DEBUG : nfs: FromHandle: handle=0F83C09216C342ED92C1516F387EB179
2024/08/21 10:00:54 DEBUG : nfs: >FromHandle: path=[], err=Invalid file handle
2024/08/21 10:00:54 DEBUG : [NFS DEBUG] request: RPC #1628752895 (nfs.Access)
2024/08/21 10:00:54 DEBUG : nfs: FromHandle: handle=0F83C09216C342ED92C1516F387EB179
2024/08/21 10:00:54 DEBUG : nfs: >FromHandle: path=[], err=Invalid file handle
2024/08/21 10:00:54 DEBUG : [NFS DEBUG] request: RPC #1628752896 (nfs.Access)
2024/08/21 10:00:54 DEBUG : nfs: FromHandle: handle=0F83C09216C342ED92C1516F387EB179
2024/08/21 10:00:54 DEBUG : nfs: >FromHandle: path=[], err=Invalid file handle
2024/08/21 10:00:54 DEBUG : [NFS DEBUG] request: RPC #1628752897 (nfs.Access)
2024/08/21 10:00:54 DEBUG : nfs: FromHandle: handle=0F83C09216C342ED92C1516F387EB179
2024/08/21 10:00:54 DEBUG : nfs: >FromHandle: path=[], err=Invalid file handle
2024/08/21 10:00:54 DEBUG : [NFS DEBUG] request: RPC #1628752898 (nfs.Access)
2024/08/21 10:00:54 DEBUG : nfs: FromHandle: handle=0F83C09216C342ED92C1516F387EB179
2024/08/21 10:00:54 DEBUG : nfs: >FromHandle: path=[], err=Invalid file handle
2024/08/21 10:00:54 DEBUG : [NFS DEBUG] request: RPC #1628752899 (nfs.Access)
2024/08/21 10:00:54 DEBUG : nfs: FromHandle: handle=0F83C09216C342ED92C1516F387EB179
2024/08/21 10:00:54 DEBUG : nfs: >FromHandle: path=[], err=Invalid file handle
2024/08/21 10:00:54 DEBUG : [NFS DEBUG] request: RPC #1628752900 (nfs.Access)
2024/08/21 10:00:54 DEBUG : nfs: FromHandle: handle=0F83C09216C342ED92C1516F387EB179
2024/08/21 10:00:54 DEBUG : nfs: >FromHandle: path=[], err=Invalid file handle
2024/08/21 10:00:54 DEBUG : [NFS DEBUG] request: RPC #1628752901 (nfs.Access)
2024/08/21 10:00:54 DEBUG : nfs: FromHandle: handle=0F83C09216C342ED92C1516F387EB179
2024/08/21 10:00:54 DEBUG : nfs: >FromHandle: path=[], err=Invalid file handle
2024/08/21 10:00:54 DEBUG : [NFS DEBUG] request: RPC #1628752902 (nfs.Access)
2024/08/21 10:00:54 DEBUG : nfs: FromHandle: handle=0F83C09216C342ED92C1516F387EB179
2024/08/21 10:00:54 DEBUG : nfs: >FromHandle: path=[], err=Invalid file handle
2024/08/21 10:00:56 DEBUG : [NFS DEBUG] request: RPC #1628752903 (nfs.GetAttr)
2024/08/21 10:00:56 DEBUG : nfs: FromHandle: handle=36AC9F2B18094C61AFFA050948BCE103
2024/08/21 10:00:56 DEBUG : nfs: >FromHandle: path=["filescom-product" "Claudio"], err=<nil>
2024/08/21 10:00:56 DEBUG : filescom-product/Claudio: Lstat:
2024/08/21 10:00:56 DEBUG : filescom-product/Claudio: >Lstat: fi=filescom-product/Claudio/, err=<nil>
2024/08/21 10:01:01 DEBUG : [NFS DEBUG] request: RPC #1628752904 (nfs.GetAttr)
#### How to use GitHub
* Please use the đź‘Ť [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to show that you are affected by the same issue.
* Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
* Subscribe to receive notifications on status change and new comments.
It reminds me that I should send PR re FUSE-T as existing one is really outdated
but the easiest is to use brew
- because then it is super easy to always update it to the latest version (it is also under active dev with improvements and fixes released quite often)
1 Like
amarder
(Andrew Marder)
November 8, 2024, 5:23pm
5
I've installed FUSE-T using brew
and the rclone binary available at Rclone downloads
I run this command:
rclone mount --vfs-cache-mode full local:/Users/amarder/Desktop ~/my-mount
When I copy a file into my-mount
I get the following error (dialog box):
The operation can’t be completed because an unexpected error occurred (error code 100093).
It looks like the Cryptomator community has hit this issue before:
I followed all of the install instructions to set up Cryptomator today on macOS Sequoia with the vault located in iCloud. Everything worked fine until I tried copying over some files and then the following error was thrown: The operation can’t be...
Reading time: 1 mins đź•‘
Likes: 1 ❤
I'll see what I can figure out...
amarder
(Andrew Marder)
November 8, 2024, 5:35pm
6
This comment got rid of the error message for me:
opened 09:08PM - 07 Sep 24 UTC
closed 11:36AM - 18 Sep 24 UTC
type:bug
state:confirmed
os:mac
state:has-workaround
misc:filesystem
mount:fuse
### Please agree to the following
- [X] I have searched [existing issues](https… ://github.com/cryptomator/cryptomator/issues?q=) for duplicates
- [X] I agree to follow this project's [Code of Conduct](https://github.com/cryptomator/cryptomator/blob/develop/.github/CODE_OF_CONDUCT.md)
### Summary
Copying to Cryptomator vault in macOS Finder fails with "unexpected error 100093"
### What software is involved?
- Operating System: macOS 15.0 (Sequoia public beta)
- Cryptomator: 1.13.0
### Volume Type
FUSE-T
### Steps to Reproduce
1. Unlock a Cryptomator vault using the GUI
2. Open the vault in Finder
3. Copy a file (tried .pdf, .txt and .md) from a folder on the Mac (e.g. Downloads folder) into the vault using command-c
### Expected Behavior
The file is now stored in the vault.
### Actual Behavior
A Finder model pops up, stating that "... an unexpected error occurred (error 100093)". In the vault, a file with the correct file name is created. However, it is empty (no content, file size shown as 0 KB).
### Reproducibility
Always
### Relevant Log Output
_No response_
### Anything else?
_No response_
I've modified my rclone command to:
rclone mount -o nonamedattr --vfs-cache-mode full local:/Users/amarder/Desktop ~/my-mount
1 Like
Thank you for sharing. So it needs some FUSE-T extra flags. I will try to add this to docs as well.
1 Like
system
(system)
Closed
December 8, 2024, 6:25pm
8
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.