Welcome to the Tweaking4All community forums!
When participating, please keep the Forum Rules in mind!
Topics for particular software or systems: Start your topic link with the name of the application or system.
For example “MacOS X – Your question“, or “MS Word – Your Tip or Trick“.
Please note that switching to another language when reading a post will not bring you to the same post, in Dutch, as there is no translation for that post!
I'm still looking for my first coffee this morning, so apologies if you already posted this:
How does mounting work (from Terminal) when using
mount_nfs -o nfc "dxp4800-plus.fritz.box:/mnt/nvme/backup" "/Users/christian/mnt/mnt_nvme_backup (dxp4800-plus.fritz.box)"
And then the next one in the same format?
Not sure if it shows an error or if it just works.
Apple ruined the API call (vs Command line option) for mounting to a custom path in one of the earlier Tahoe versions - otherwise we could try that one.
I did submit a bug report for that and they said they fixed it, they just failed to mention what macOS version.
I'll try and see if I can find some time this week to run a test with that - for all I know this may resolve your issue.
Hi Hans,
Now it works. There was a missing parameter in the command line:
With the following option it works:
-o nfc -o vers=4
So I added only to use NFS version 4.
Best regards
Christian
Oh wow! Nice find! 👍
No way I would have found that out on own. Thank you for finding that!
Not expecting you to test this, but with those parameters: does this work on both ConnectMeNow versions? Or did you only try the test version I had posted?
(I'm considering adding this as the default for NFS mounts)
Hi Hans
I can test it with the previous version on Friday.
But I think that the change you made is still necessary.
Best regards
Christian
And thank you for bringing me a quick solution for my problem. Very good!
Hi Christian,
But I think that the change you made is still necessary.
That's what I suspected and wanted to make sure of before publishing a new release 😊
I'll wait for your reply/test before publishing something but for now I'll prepare the test version with the parameters you found.
Excellent help!
And thank you for bringing me a quick solution for my problem. Very good!
You're most welcome 😊
Always nice to work with users that are willing to help!
Hello Hans,
I installed the prior version (4.0.23 Build 86) with the same settings.
But with this prior version there is still the same issue because the directory "/Users/christian/mnt/mnt" used as mount point for the first NFS share is already used.
I am sure that it only works, if the whole share name is used as subdirectory as you already implemented it in the test version.
Best regards
Christian
I have 4.0.25 prepared with the same path we used in the test version.
The options you had figured out are now the default mount options for NFS when creating a new NFS share.
I would have not figured this one out without your help - thank you 😊
Note:
Not relevant to your issue, but I also re-enabled the option to use custom mount points when using the systemcall (API) Mount Style.
Apple broke this function in the latest Tahoe versions. I had reported this as a bug, and Apple replied weeks later that it had addressed the issue, but conveniently didn't mention in what release it would be included. In Tahoe 26.5.1 it still does not work - so I added a hint that cautions the user from using that option.
Thank you again for your help 😊
Just published 4.0.25 with the changes 😊
Hello Hans,
Thank you - I installed this version right now.
Best regards
Christian
Let me know if you run into issue 😊
