| 2015-09-07 14:58:09 |
Ramana Raja |
description |
The glusterfs share driver that uses NFS Ganesha server to mediate access to the shares, displays the wrong export location.
$
$
$ manila list
ID | Name | Size | Share Proto | Status | Is Public | Share Type | Export location
dbeba93f-a1a1-4143-8602-c42162a00ab6 | None | 1 | NFS | available | False | glusterfs_ganesha | root@172.16.53.14:/manila-nfs-volume/share-af60ed90-b5d9-426b-bbc4-6cfeef63c2c0
$
$showmount -e 172.16.53.14
Export list for 172.16.53.14:
/share-af60ed90-b5d9-426b-bbc4-6cfeef63c2c0 172.16.53.73
$ sudo mount -t nfs -o vers=4 root@172.16.53.14:/manila-nfs-volume/share-af60ed90-b5d9-426b-bbc4-6cfeef63c2c0 /mnt/nfsv4
mount.nfs: Failed to resolve server root@172.16.53.14: No address associated with hostname
$
$ sudo mount -t nfs -o vers=4 172.16.53.14:/manila-nfs-volume/share-af60ed90-b5d9-426b-bbc4-6cfeef63c2c0 /mnt/nfsv4
mount.nfs: access denied by server while mounting 172.16.53.14:/manila-nfs-volume/share-af60ed90-b5d9-426b-bbc4-6cfeef63c2c0
$
$ sudo mount -t nfs -o vers=4 172.16.53.14:/share-af60ed90-b5d9-426b-bbc4-6cfeef63c2c0 /mnt/nfsv4
$ mount
172.16.53.14:/share-af60ed90-b5d9-426b-bbc4-6cfeef63c2c0 on /mnt/nfsv4 type nfs
$
$
The actual NFS export location and the export location displayed using Manila CLI are not the same. The Manila command displays the export location with the following syntax,,
[root@]<host-ip>:/<volname>/<share-shareid>
when it actually should be,
<host-ip>:/<share-shareid> |
The glusterfs share driver that uses NFS Ganesha server to mediate access to the shares, displays the wrong export location.
$
$
$ manila list
ID | Name | Size | Share Proto | Status | Is Public | Share Type | Export location
dbeba93f-a1a1-4143-8602-c42162a00ab6 | None | 1 | NFS | available | False | glusterfs_ganesha | root@172.16.53.14:/manila-nfs-volume/share-af60ed90-b5d9-426b-bbc4-6cfeef63c2c0
$
$s howmount -e 172.16.53.14
Export list for 172.16.53.14:
/share-af60ed90-b5d9-426b-bbc4-6cfeef63c2c0 172.16.53.73
$ sudo mount -t nfs -o vers=4 root@172.16.53.14:/manila-nfs-volume/share-af60ed90-b5d9-426b-bbc4-6cfeef63c2c0 /mnt/nfsv4
mount.nfs: Failed to resolve server root@172.16.53.14: No address associated with hostname
$
$ sudo mount -t nfs -o vers=4 172.16.53.14:/manila-nfs-volume/share-af60ed90-b5d9-426b-bbc4-6cfeef63c2c0 /mnt/nfsv4
mount.nfs: access denied by server while mounting 172.16.53.14:/manila-nfs-volume/share-af60ed90-b5d9-426b-bbc4-6cfeef63c2c0
$
$ sudo mount -t nfs -o vers=4 172.16.53.14:/share-af60ed90-b5d9-426b-bbc4-6cfeef63c2c0 /mnt/nfsv4
$ mount
172.16.53.14:/share-af60ed90-b5d9-426b-bbc4-6cfeef63c2c0 on /mnt/nfsv4 type nfs
$
$
The actual NFS export location and the export location displayed using Manila CLI are not the same. The Manila command displays the export location with the following syntax,,
[root@]<host-ip>:/<volname>/<share-shareid>
when it actually should be,
<host-ip>:/<share-shareid> |
|
| 2015-09-07 14:58:29 |
Ramana Raja |
description |
The glusterfs share driver that uses NFS Ganesha server to mediate access to the shares, displays the wrong export location.
$
$
$ manila list
ID | Name | Size | Share Proto | Status | Is Public | Share Type | Export location
dbeba93f-a1a1-4143-8602-c42162a00ab6 | None | 1 | NFS | available | False | glusterfs_ganesha | root@172.16.53.14:/manila-nfs-volume/share-af60ed90-b5d9-426b-bbc4-6cfeef63c2c0
$
$s howmount -e 172.16.53.14
Export list for 172.16.53.14:
/share-af60ed90-b5d9-426b-bbc4-6cfeef63c2c0 172.16.53.73
$ sudo mount -t nfs -o vers=4 root@172.16.53.14:/manila-nfs-volume/share-af60ed90-b5d9-426b-bbc4-6cfeef63c2c0 /mnt/nfsv4
mount.nfs: Failed to resolve server root@172.16.53.14: No address associated with hostname
$
$ sudo mount -t nfs -o vers=4 172.16.53.14:/manila-nfs-volume/share-af60ed90-b5d9-426b-bbc4-6cfeef63c2c0 /mnt/nfsv4
mount.nfs: access denied by server while mounting 172.16.53.14:/manila-nfs-volume/share-af60ed90-b5d9-426b-bbc4-6cfeef63c2c0
$
$ sudo mount -t nfs -o vers=4 172.16.53.14:/share-af60ed90-b5d9-426b-bbc4-6cfeef63c2c0 /mnt/nfsv4
$ mount
172.16.53.14:/share-af60ed90-b5d9-426b-bbc4-6cfeef63c2c0 on /mnt/nfsv4 type nfs
$
$
The actual NFS export location and the export location displayed using Manila CLI are not the same. The Manila command displays the export location with the following syntax,,
[root@]<host-ip>:/<volname>/<share-shareid>
when it actually should be,
<host-ip>:/<share-shareid> |
The glusterfs share driver that uses NFS Ganesha server to mediate access to the shares, displays the wrong export location.
$
$
$ manila list
ID | Name | Size | Share Proto | Status | Is Public | Share Type | Export location
dbeba93f-a1a1-4143-8602-c42162a00ab6 | None | 1 | NFS | available | False | glusterfs_ganesha | root@172.16.53.14:/manila-nfs-volume/share-af60ed90-b5d9-426b-bbc4-6cfeef63c2c0
$
$ showmount -e 172.16.53.14
Export list for 172.16.53.14:
/share-af60ed90-b5d9-426b-bbc4-6cfeef63c2c0 172.16.53.73
$ sudo mount -t nfs -o vers=4 root@172.16.53.14:/manila-nfs-volume/share-af60ed90-b5d9-426b-bbc4-6cfeef63c2c0 /mnt/nfsv4
mount.nfs: Failed to resolve server root@172.16.53.14: No address associated with hostname
$
$ sudo mount -t nfs -o vers=4 172.16.53.14:/manila-nfs-volume/share-af60ed90-b5d9-426b-bbc4-6cfeef63c2c0 /mnt/nfsv4
mount.nfs: access denied by server while mounting 172.16.53.14:/manila-nfs-volume/share-af60ed90-b5d9-426b-bbc4-6cfeef63c2c0
$
$ sudo mount -t nfs -o vers=4 172.16.53.14:/share-af60ed90-b5d9-426b-bbc4-6cfeef63c2c0 /mnt/nfsv4
$ mount
172.16.53.14:/share-af60ed90-b5d9-426b-bbc4-6cfeef63c2c0 on /mnt/nfsv4 type nfs
$
$
The actual NFS export location and the export location displayed using Manila CLI are not the same. The Manila command displays the export location with the following syntax,,
[root@]<host-ip>:/<volname>/<share-shareid>
when it actually should be,
<host-ip>:/<share-shareid> |
|
