On 06/14/2014 11:38 AM, Alexey Zilber wrote:
Hi All,
I'm having a horrid time getting gluster to create a volume.
Initially, I messed up a path and had the error mentioned here:
http://joejulian.name/blog/glusterfs-path-or-a-prefix-of-it-is-already-part-of-a-volume/
I fixed it, restarted gluster on both nodes, and then I just get a
straight up failure:
# gluster volume create devroot replica 2 transport tcp
sfdev1:/data/brick1/devroot sfdev2:/data/brick1/devroot
volume create: devroot: failed
The only thing that gets created are the extended attributes in
/data/brick1/devroot on sfdev1.
Here's the cli.log.. not much in there:
---
[2014-06-14 05:42:03.519769] W [rpc-transport.c:175:rpc_transport_load]
0-rpc-transport: missing 'option transport-type'. defaulting to "socket"
[2014-06-14 05:42:03.523525] I [socket.c:3480:socket_init] 0-glusterfs:
SSL support is NOT enabled
[2014-06-14 05:42:03.523580] I [socket.c:3495:socket_init] 0-glusterfs:
using system polling thread
[2014-06-14 05:42:03.600482] I
[cli-cmd-volume.c:392:cli_cmd_volume_create_cbk] 0-cli: Replicate
cluster type found. Checking brick order.
[2014-06-14 05:42:03.600844] I
[cli-cmd-volume.c:304:cli_cmd_check_brick_order] 0-cli: Brick order okay
[2014-06-14 05:42:03.668257] I
[cli-rpc-ops.c:805:gf_cli_create_volume_cbk] 0-cli: Received resp to
create volume
[2014-06-14 05:42:03.668365] I [input.c:36:cli_batch] 0-: Exiting with: -1
---
.cmd_log_history shows:
[2014-06-14 05:42:03.668051]: volume create devroot replica 2 transport
tcp sfdev1:/data/brick1/devroot sfdev2:/data/brick1/devroot : FAILED :
etc-glusterfs-glusterd.vol.log seems good too.
Can you please check again the part relating to the attempt to create
volume devroot in glusterd.vol.log? glusterd's log file normally
contains information regarding why an operation failed.
-Vijay
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users
