#Help with setting multiple NFS options with JSON backend.
1 messages · Page 1 of 1 (latest)
The NFS mount options are a string, and they work exactly the same as with the "-o" option to the "mount" command in Linux. I.e. you can set them to "rsize=65536,wsize=65536,hard,nolock"
this is what I have currently:
{
"version": 1,
"storageDriverName": "ontap-nas-flexgroup",
"backendName": "tbc-ontap-nas-flexgroup",
"managementLIF": "172.23.67.20",
"dataLIF": "172.23.71.253",
"svm": "svm-ctlabshared-tri01",
"username": "vsadmin",
"password": "netapp123!",
"limitAggregateUsage": "85%",
"limitVolumeSize": "50Ti",
"spaceReserve": "none",
"autoExportCIDRs": ["172.23.71.0/24"],
"autoExportPolicy": true,
"nfsMountOptions": "nfsvers=4.1, wsize=262144, rsize=262144, nconnect=8",
"storagePrefix": "nfs_fg_trident_",
"snapshotPolicy": "default"
}
so I can just delete the snapces under nfsmountoptions?
ok will try again. It appeared to only mount using the first option nfsv4.1 and ignored the rest but let me try again. Thanks for helping 🙂
Some of those, like spaceReserve and snapshotPolicy, belong in a defaults section. See https://docs.netapp.com/us-en/trident/trident-use/ontap-nas-examples.html#backend-configuration-options-for-provisioning-volumes
Thanks! I did see that under some of the sample set. I will update them as well.
Thanks guys for the help! all the options are working as intended!
Can I ask if there is a preference or benefit for configuring backends using tridentctl vs kubectl?
Personally, I prefer doing everything with kubectl, as I don't need another binary for that (and tridentctl is x86-only so I can't use it on my RaspberryPi for example 😉 )