Re: [Gluster-devel] Cannot run VMware Virtual Machines on GlusterFS

[Tomoaki Sato]

Vijay,

I've reproduce the issue in my environment.
getcwd fail on the ESXi host when the NFS server is GlusterFS.


with a Linux kernel NFS server:

~ # uname
VMkernel
~ # esxcfg-nas -l
~ # esxcfg-nas -a -o 192.168.1.254 -s /mnt/brick centos_nfs
Connecting to NAS volume: centos_nfs
centos_nfs created and connected.
~ # df | grep nfs
nfs                  471110552 430269304  16524116  96% 
/vmfs/volumes/94925201-78f190e0
~ # find /vmfs/volumes/94925201-78f190e0
/vmfs/volumes/94925201-78f190e0
~ # mkdir /vmfs/volumes/94925201-78f190e0/foo
~ # cd /vmfs/volumes/94925201-78f190e0/foo
/vmfs/volumes/94925201-78f190e0/foo # cd
~ # rmdir /vmfs/volumes/94925201-78f190e0/foo
~ # esxcfg-nas -d centos_nfs
NAS volume centos_nfs deleted.

with a GlusterFS(NFS) :

~ # uname
VMkernel
~ # esxcfg-nas -l
~ # esxcfg-nas -a -o 192.168.1.136 -s /bar gluster_nfs
Connecting to NAS volume: gluster_nfs
gluster_nfs created and connected.
~ # df | grep nfs
nfs                  104722720    195396  104527324   0% 
/vmfs/volumes/ef172a87-e5ae817f
~ # find /vmfs/volumes/ef172a87-e5ae817f
/vmfs/volumes/ef172a87-e5ae817f
/vmfs/volumes/ef172a87-e5ae817f/lost+found
~ # mkdir /vmfs/volumes/ef172a87-e5ae817f/bar
~ # cd /vmfs/volumes/ef172a87-e5ae817f/bar
ash: getcwd: No such file or directory
(unknown) # cd
~ # rmdir /vmfs/volumes/ef172a87-e5ae817f/bar
~ # esxcfg-nas -d gluster_nfs
NAS volume gluster_nfs deleted.
~ #

# rpm -qa | grep gluster
glusterfs-fuse-3.3.0-1
glusterfs-3.3.0-1
glusterfs-debuginfo-3.3.0-1
glusterfs-server-3.3.0-1
# gluster volume info
 
Volume Name: bar
Type: Distribute
Volume ID: b2d75589-8370-4528-ab4e-b543b3abdc3b
Status: Started
Number of Bricks: 1
Transport-type: tcp
Bricks:
Brick1: bar-1-private:/mnt/brick
Options Reconfigured:
diagnostics.client-log-level: TRACE
diagnostics.brick-log-level: TRACE


Tomo Sato


Fernando Frediani (Qube) wrote:
> Hi,
>
> I have been trying to run VMware ESXi VMs on Gluster and was never able to, 
> either with Gluster 3.2 or 3.3. It mounts the NFS, deploy the VM but can’t 
> power it on. I suspect it would be something to do with the way Gluster exports 
> NFS.
>
> I have been people reporting that they used it with KVM VMs and normal Linux 
> NFS, but I never saw anyone saying they have used it with VMware.
>
> I have enabled TRACE logging and grabber the logs from the host I mounted the 
> Datastore while trying to power on the VM.
>
> Would someone care to look and confirm if it’s a NFS export problem or if the 
> problem is somewhere else ?
>
> Thanks
>
> Regards,
>
> *Fernando Frediani*
>
>
>
> _______________________________________________
> Gluster-devel mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/gluster-devel