Gluster users - Jan 2013 - hanging of mounted filesystem (3.3.1)

Hi All ~

	I created an eight-brick gluster 3.3.1 volume (2x replication) on
eight CentOS 6.3 x64 systems. I was able to form and start the volume
without issue. I was also able to mount it through /etc/fstab as a native
glusterfs mount. I have a couple questions issues at this point:

	- On a client machine, "glusterfs" is not recognized as a valid type
unless gluster-server is installed. This seems to contradict the
documentation - wanted to make sure I'm not doing something wrong. More a
clarification than issue here. 

	- The glusterfs process is taking between 50% and 80% CPU on both
the brick and client systems (these are fairly powerful, brand new servers).


	- No doubt linked to the above, the mounted filesystem hangs
indefinitely when accessed. I tried an "ls -a" on the mounted
filesystem,
for example, which hangs forever. I tested this by mounting a brick system
to itself and to a client which is not a brick and the same behavior was
observed. Both were glusterfs mounts. 

	There is nothing special about my deployment except for the use of
transport = tcp,rdma. I am running on Ethernet now but will be migrating to
Infiniband after this is debugged. 

	Thanks for any advice,
	~Mike C.

Hi All ~

 

            I created an eight-brick gluster 3.3.1 volume (2x replication)
on eight CentOS 6.3 x64 systems. I was able to form and start the volume
without issue. I was also able to mount it through /etc/fstab as a native
glusterfs mount. I have a couple questions issues at this point:

 

            - On a client machine, "glusterfs" is not recognized as a
valid
type unless gluster-server is installed. This seems to contradict the
documentation - wanted to make sure I'm not doing something wrong. More a
clarification than issue here. 

 

            - The glusterfs process is taking between 50% and 80% CPU on
both the brick and client systems (these are fairly powerful new servers).

 

            - No doubt linked to the above, the mounted filesystem hangs
indefinitely when accessed. I tried an "ls -a" on the mounted
filesystem,
for example, which hangs forever. I tested this by mounting a brick system
to itself and to a client which is not a brick and the same behavior was
observed. Both were glusterfs mounts. 

 

            There is nothing special about my deployment except for the use
of transport = tcp,rdma. I am running on Ethernet now but will be migrating
to Infiniband after this is debugged. 

 

            Thanks for any advice,

                ~Mike C.

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://supercolony.gluster.org/pipermail/gluster-users/attachments/20130131/01abeda7/attachment.html>

Hi All ~

 

            I created an eight-brick gluster 3.3.1 volume (2x replication)
on eight CentOS 6.3 x64 systems. I was able to form and start the volume
without issue. I was also able to mount it through /etc/fstab as a native
glusterfs mount. I have a couple questions issues at this point:

 

            - On a client machine, "glusterfs" is not recognized as a
valid
type unless gluster-server is installed. This seems to contradict the
documentation - wanted to make sure I'm not doing something wrong. More a
clarification than issue here. 

 

            - The glusterfs process is taking between 50% and 80% CPU on
both the brick and client systems (these are fairly powerful new servers).

 

            - No doubt linked to the above, the mounted filesystem hangs
indefinitely when accessed. I tried an "ls -a" on the mounted
filesystem,
for example, which hangs forever. I tested this by mounting a brick system
to itself and to a client which is not a brick and the same behavior was
observed. Both were glusterfs mounts. 

 

            There is nothing special about my deployment except for the use
of transport = tcp,rdma. I am running on Ethernet now but will be migrating
to Infiniband after this is debugged. 

 

            Thanks for any advice,

                ~Mike C.

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://supercolony.gluster.org/pipermail/gluster-users/attachments/20130131/8d46daf2/attachment.html>

remove the transport rdma and try again. When using RDMA I've also had
extremely bad CPU eating issues.

I currently run gluster with IPoIB to get the speed of infiniband and the
non-crazy cpu usage of rdma gluster.


On Thu, Jan 31, 2013 at 9:20 AM, Michael Colonno <mike at
hpccloudsolutions.com
> wrote:
>         Hi All ~
>
>         I created an eight-brick gluster 3.3.1 volume (2x replication) on
> eight CentOS 6.3 x64 systems. I was able to form and start the volume
> without issue. I was also able to mount it through /etc/fstab as a native
> glusterfs mount. I have a couple questions issues at this point:
>
>         - On a client machine, "glusterfs" is not recognized as a
valid
> type
> unless gluster-server is installed. This seems to contradict the
> documentation - wanted to make sure I'm not doing something wrong. More
a
> clarification than issue here.
>
>         - The glusterfs process is taking between 50% and 80% CPU on both
> the brick and client systems (these are fairly powerful, brand new
> servers).
>
>
>         - No doubt linked to the above, the mounted filesystem hangs
> indefinitely when accessed. I tried an "ls -a" on the mounted
filesystem,
> for example, which hangs forever. I tested this by mounting a brick system
> to itself and to a client which is not a brick and the same behavior was
> observed. Both were glusterfs mounts.
>
>         There is nothing special about my deployment except for the use of
> transport = tcp,rdma. I am running on Ethernet now but will be migrating to
> Infiniband after this is debugged.
>
>         Thanks for any advice,
>         ~Mike C.
>
>
>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://supercolony.gluster.org/mailman/listinfo/gluster-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://supercolony.gluster.org/pipermail/gluster-users/attachments/20130131/38789e49/attachment.html>

Tried the proto=tcp setting, same error unfortunately...

	Thanks,
	~Mike C. 

-----Original Message-----
From: Robert Hajime Lanning [mailto:lanning at lanning.cc] 
Sent: Thursday, January 31, 2013 4:28 PM
To: Michael Colonno
Cc: gluster-users at gluster.org
Subject: Re: [Gluster-users] hanging of mounted filesystem (3.3.1)

On 01/31/13 15:54, Michael Colonno wrote:
> Updating this thread: I tried to switch over to NFS mounting. When I 
> try to mount the volume with the following line in fstab:
>
> node1:/Volume /tmp/mnt nfs defaults,_netdev,vers=3 0 0
node1:/Volume /tmp/mnt nfs defaults,_netdev,vers=3,proto=tcp 0 0

--
Mr. Flibble
King of the Potato People