Sorry, but the test what I did was in a system that has a old version
of glusterfs (3.4.0).
And I didn't had saw this.
On 19-12-2014 09:55, Volnei Puttini wrote:
Vijay,
A fact about the problem, which doesn't know if any
of you have noticed, is that if we do the mounting
volume via the /etc/fstab, the problem doesn't happens.
The mount is successful.
/etc/fstab
g01:/vgtest /mnt/gluster glusterfs defaults,_netdev 0 0
On 18-12-2014 15:55, Vijay Bellur wrote:
On 12/18/2014 06:29 PM, Volnei Puttini wrote:
Hi,
Could anyone tell me why the error below happens?
I got to see some documents on this, but nothing
conclusively or to indicate how to solve the issue.
CentOS 7
glusterfs 3.6.1 built on Nov 7 2014 15:16:40
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GlusterFS under the terms of the GNU
General Public License.
----------------------------------------------------------------------------
Volume Name: vgtest
Type: Replicate
Volume ID: 63e18f64-ff0e-4866-b341-24c6f20c0677
Status: Started
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: g01:/glusterfs/brick1/data
Brick2: g02:/glusterfs/brick1/data
Options Reconfigured:
auth.allow: 192.168.2.*
----------------------------------------------------------------------------
/usr/sbin/glusterfs --debug --attribute-timeout=1 --volfile-server=g01
--volfile-id=/glusterfs/brick1/data/ /mnt/Storage0
[2014-12-18 12:52:21.685720] I [MSGID: 100030] [glusterfsd.c:2018:main]
0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version
3.6.1
(args: /usr/sbin/glusterfs --debug --attribute-timeout=1
--volfile-server=g01 --volfile-id=/glusterfs/brick1/data/
/mnt/Storage0)
[2014-12-18 12:52:21.686120] D [MSGID: 0]
[glusterfsd.c:409:set_fuse_mount_options] 0-glusterfsd:
fopen-keep-cache
mode 2
[2014-12-18 12:52:21.686140] D [MSGID: 0]
[glusterfsd.c:463:set_fuse_mount_options] 0-glusterfsd: fuse direct io
type 2
[2014-12-18 12:52:21.686153] D [MSGID: 0]
[glusterfsd.c:487:set_fuse_mount_options] 0-glusterfsd: fuse
no-root-squash mode 0
[2014-12-18 12:52:21.686243] D
[options.c:1163:xlator_option_init_double] 0-fuse: option
attribute-timeout using set value 1,000000
[2014-12-18 12:52:21.686268] I
[options.c:1163:xlator_option_init_double] 0-fuse: option entry-timeout
convertion failed value 1.0
[2014-12-18 12:52:21.686279] E [xlator.c:425:xlator_init] 0-fuse:
Initialization of volume 'fuse' failed, review your volfile again
[2014-12-18 12:52:21.686290] D [MSGID: 0]
[glusterfsd.c:572:create_fuse_mount] 0-glusterfsd: failed to initialize
fuse translator
Seems related to the locale issue being discussed on this list
previously [1]. The discussion also has a workaround.
This issue should be fixed in 3.6.2.
-Vijay
[1] http://gluster.org/pipermail/gluster-users/2014-November/019603.html
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users
