[
https://issues.apache.org/jira/browse/CLOUDSTACK-9252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15113710#comment-15113710
]
ASF GitHub Bot commented on CLOUDSTACK-9252:
--------------------------------------------
Github user rafaelweingartner commented on the pull request:
https://github.com/apache/cloudstack/pull/1361#issuecomment-174177981
Hi @ nvazquez,
Are you sure that the problem is caused because we are not telling the NFS
protocol version to the mount command?
If you a look at the doc in [1] and [2], you will see that if we do not
provide a NFS protocol version to be used, it (the mount program) will first
try version 4, then 3, and version 2 as the last one.
If the default behavior of mount is to try every possible protocol
available, I do not see why we need to add some extra code to enable us to
specify one.
Wasn’t your problem caused by something else?
[1] http://man7.org/linux/man-pages/man8/mount.8.html
[2] http://man7.org/linux/man-pages/man5/nfs.5.html#MOUNT_OPTIONS
> 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)
