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
I get:
mount.nfs: mounting node1:/Volume failed, reason given by
server:
No such file or directory
It seems from the documentation that the mount folder is
supposed to be the gluster volume name. I also assume I don't need an
exports entry since there is nothing in the documentation about this and the
volume options seem to indicate that My gluster volume itself seems to start
and stop without any issue but can't seem to mount via any method(?)
Hopefully I am just doing something simple wrong in config; I have tried to
meticulously follow the admin guide. For reference here is my volume info:
Volume Name: Volume
Type: Distributed-Replicate
Volume ID: 409d4096-feda-4b5f-b01b-3383d39af1c6
Status: Started
Number of Bricks: 4 x 2 = 8
Transport-type: tcp,rdma
Bricks:
Brick1: node1:/volume
Brick2: node2:/volume
Brick3: node3:/volume
Brick4: node4:/volume
Brick5: node5:/volume
Brick6: node6:/volume
Brick7: node7:/volume
Brick8: node8:/volume
Thanks,
~Mike C.
From: gluster-users-bounces at gluster.org
[mailto:gluster-users-bounces at gluster.org] On Behalf Of Michael Colonno
Sent: Thursday, January 31, 2013 2:41 PM
To: gluster-users at gluster.org
Subject: Re: 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 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/6910bf2a/attachment-0001.html>
