cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remi Bergsma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-7414) SSVM 4.4.0-6 fails to connect to NFS v3 and v4.1 shares
Date Fri, 20 Feb 2015 17:20:13 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-7414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329201#comment-14329201
] 

Remi Bergsma commented on CLOUDSTACK-7414:
------------------------------------------

Disable NFSv4 on Windows, it will then work with NFSv3 just fine.

> SSVM 4.4.0-6 fails to connect to NFS v3 and v4.1 shares
> -------------------------------------------------------
>
>                 Key: CLOUDSTACK-7414
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7414
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: SystemVM
>    Affects Versions: 4.4.0
>         Environment: CloudStack v4.4 with SystemTemplate 4.4.0-6
> Deafult SSVM over Debian
> Windows Storage Server 2012 with NFS running ver 3 or 4.1
> VMWare 5.5
>            Reporter: Gaur Sunder
>            Priority: Critical
>              Labels: NFSv3, NFSv4.1, secondary_storage, ssvm
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Secondary Storage is provided on Windows Storage Server 2012. NFS Service is installed
and working. Note that WSS 2012 supports NFS v3 and v4.1 but not v4 (for whatever reason they
may have)
> Able to add Secondary Storage using CS UI.
> SSVM starts but fails to load the Secondary Storage. Checked with ssvm-check.sh saying
Error: "NFS is not currently mounted" and "NFS Server is 0.0.0.0"
> Manually mounting NFS location with "mount -t nfs -o vers=3" or "mount -t nfs -o minorversion=1"
successfully loads the storage location.
> Tried setting /etc/nfsmount.conf with Defaultvers=3 or Defaultvers=4.1 but appears SSVM
ignores nfsmount.conf file.
> Can add manual entry in /etc/fstab but not sure if that is going to work in SSVM as while
mounting it creates a uuid location dynamically.
> There is no way to supply mount options to SSVM and SSVM is not automatically degrading
to v3 if v4 is not successful.
> There should be a way to either pass mount options to SSVM or some script/setting that
can be edited/provided to work.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message