[
https://issues.apache.org/jira/browse/CLOUDSTACK-9252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115386#comment-15115386
]
Sergey Levitskiy commented on CLOUDSTACK-9252:
----------------------------------------------
Unfortunately NFS version negotiation doesn't work properly with all storage
vendors. Some vendors e.g. Tintri require that vers=3 is supplied in mount
command likely due to the fact they don't support negotiations on the server
side.
When such NFS secondary storages tries to get mounted in SSVM an exception in
mount is generated
'mount.nfs: Protocol family not supported'
The same happens when trying to mount in shell so mount command needs to be
told a specific version. If done so mount succeeds in both management server as
well as in SSVM. Supporting nfs.version in image_store_details gives the best
option to support great variety of NFS storage vendors without bluntly relying
on version negotiation in nfs.mount.
> Support configurable NFS version for Secondary Storage mounts
> -------------------------------------------------------------
>
> Key: CLOUDSTACK-9252
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9252
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
> Reporter: Nicolas Vazquez
>
> After starting secondary storage VM, secondary storage tries to be mounted
> but fails with error: {{Protocol family not supported}}
> It was found out that adding {{-o vers=X}} to mount command it would work,
> where {{X}} is the desired NFS version to use.
> If it is desired to mount a store with a specific NFS version, it has passed
> in {{image_store_details}} table for a store with id {{Y}} as a property:
> ||store_id||||name||value||
> |Y|nfs.version|X|
> Where X stands for NFS version
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
