This has to do with locales. My locale is danish thus using comma for doubles.
When running with LANG=da_DK.UTF-8, the LC_NUMERIC is set to da_DK.UTF-8
sudo /usr/local/sbin/glusterfs --debug --entry-timeout=1 --volfile-server=bd --volfile-id=dist-rep /mnt/glusterfs/
[2014-10-25 09:45:13.131164] I [MSGID: 100030] [glusterfsd.c:2018:main] 0-/usr/local/sbin/glusterfs: Started running /usr/local/sbin/glusterfs version 3.6.0beta3 (args: /usr/local/sbin/glusterfs --debug --entry-timeout=1 --volfile-server=bd --volfile-id=dist-rep /mnt/glusterfs/)
[2014-10-25 09:45:13.131726] D [MSGID: 0] [glusterfsd.c:409:set_fuse_mount_options] 0-glusterfsd: fopen-keep-cache mode 2
[2014-10-25 09:45:13.131748] D [MSGID: 0] [glusterfsd.c:487:set_fuse_mount_options] 0-glusterfsd: fuse no-root-squash mode 0
[2014-10-25 09:45:13.131833] I [options.c:1163:xlator_option_init_double] 0-fuse: option attribute-timeout convertion failed value 1.0
[2014-10-25 09:45:13.131848] E [xlator.c:425:xlator_init] 0-fuse: Initialization of volume 'fuse' failed, review your volfile again
[2014-10-25 09:45:13.131857] D [MSGID: 0] [glusterfsd.c:572:create_fuse_mount] 0-glusterfsd: failed to initialize fuse translator
fails. Setting LANG=en_DK.UTF-8 works (LC_NUMERIC="C".
I guess the real problem is the hardcoded values (1.0) in xlators/mount/fuse/src/fuse-bridge.c, that is parsed using localised routines.
(In reply to Anders Blomdell from comment #2)
> See https://bugzilla.redhat.com/show_bug.cgi?id=1117951
Ah i remember this, and quickly forgot about it. Thanks for that :-), looks like that needs to go in 'release-3.6' branch.
Patch from Bug 1117951: http://review.gluster.org/8299
REVIEW: http://review.gluster.org/9132 (Use C-locale for numeric/string conversion routines) posted (#1) for review on release-3.6 by Niels de Vos (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/9132 committed in release-3.6 by Vijay Bellur (email@example.com)
Author: Niels de Vos <firstname.lastname@example.org>
Date: Sat Nov 15 23:40:14 2014 +0100
Use C-locale for numeric/string conversion routines
(strtod, ...) or config file parsing might fail.
Cherry picked from commit 5b8de971a4b81bc2bd6de0ffc6386587226295c6:
> Change-Id: I649f29bbf87222399a0c2d1ed5a3bf136c613b9b
> BUG: 1117951
> Signed-off-by: Anders Blomdell <email@example.com>
> Reviewed-on: http://review.gluster.org/8299
> Tested-by: Gluster Build System <firstname.lastname@example.org>
> Reviewed-by: Prashanth Pai <email@example.com>
> Reviewed-by: Vijay Bellur <firstname.lastname@example.org>
Signed-off-by: Niels de Vos <email@example.com>
Tested-by: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: Humble Devassy Chirammal <email@example.com>
Reviewed-by: Vijay Bellur <firstname.lastname@example.org>
*** Bug 1170575 has been marked as a duplicate of this bug. ***
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-v3.6.2, please open a new bug report.
glusterfs-v3.6.2 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.