Custom flags on mounts - Githubissues

dlandon / unassigned.devices

Unassigned Devices plugin for unRAID

Other

81 stars 39 forks source link

Custom flags on mounts #71

Closed andremedeiros closed 3 years ago

andremedeiros commented 3 years ago

Hi!

I was wondering if you'd consider extra options to pass to the mount point. I use this plugin for NFS shares, but there are options I'd like to set, like:

NFS Version
Write and read size
Whether I want a soft or hard mount
noatime, nodiratime

Would you consider this functionality?

dlandon commented 3 years ago

I've added the noatime and nodiratime to the mount command.

NFS version; I'll have to better understand what implications this might have. NFS has in general been a bit problematic, especially with stale file handles.
Write and read size; why do you feel this is necessary?
Hard or soft mount; this has some implications on error recovery when a remote share drops off line. Why do you feel you need this?

andremedeiros commented 3 years ago

Bigger write and read sizes improve throughput. Default is 8k, on local networks you can safely > 10x that figure.

Soft or hard is more of a hypothetical, to be honest, nice to have.

dlandon commented 3 years ago

After some research and testing, these suggestions really don't offer any value:

NFS Version. NFS negotiates the highest version the server offers. There is really no reason to specify a version.
Write and read size. NFS negotiates the highest read and write sizes supported by the server and client.
Hard or soft mount. UD sets the 'hard' mount option for best recovery. I'm not inclined to let users mess around with this parameter.
noatime, nodiratime are controlled by the NFS server and these parameters don't work on a NFS client.