Hi,
Why have you created a "disperse" volume with "0" redundancy?
There is no sense of creating this configuration of disperse volume. However, it should be noted why cli allowed it at all.
There is no sense of creating this configuration of disperse volume. However, it should be noted why cli allowed it at all.
I tried your config with the latest version and I also was not able to mount the volume.
In my case I could see the error message in logs which clearly shows that -
[2016-08-08 04:07:50.261561] I [MSGID: 101190] [event-epoll.c:628:event_dispatch_epoll_worker] 0-epoll: Started thread with index 1
[2016-08-08 04:07:50.271330] E [MSGID: 122051] [ec.c:63:ec_parse_options] 0-test-disperse-0: Invalid redundancy (must be between 1 and 3) [Invalid argument]
[2016-08-08 04:07:50.271354] E [MSGID: 122052] [ec.c:599:init] 0-test-disperse-0: Failed to parse xlator options [Invalid argument]
[2016-08-08 04:07:50.271330] E [MSGID: 122051] [ec.c:63:ec_parse_options] 0-test-disperse-0: Invalid redundancy (must be between 1 and 3) [Invalid argument]
[2016-08-08 04:07:50.271354] E [MSGID: 122052] [ec.c:599:init] 0-test-disperse-0: Failed to parse xlator options [Invalid argument]
I did not see any such message in logs provided by you.
I think you should consider using the latest version of gluster and also use a config which actually serves the purpose of disperse volume.
Ashish
From: "jayakrishnan mm" <jayakrishnan.mm@xxxxxxxxx>
To: "Ashish Pandey" <aspandey@xxxxxxxxxx>
Sent: Monday, August 8, 2016 7:39:21 AM
Subject: Re: Unable to mount (glusterfs-fuse: 2: LOOKUP() error)
To: "Ashish Pandey" <aspandey@xxxxxxxxxx>
Sent: Monday, August 8, 2016 7:39:21 AM
Subject: Re: Unable to mount (glusterfs-fuse: 2: LOOKUP() error)
Dear Ashish,
Thanks for the reply.
jk@jk:/var/log/glusterfs$ sudo gluster v info
Volume Name: dsi129-vol
Type : Disperse
Volume ID: 3537353c-f8ad-495e-bb17-0ddee4c2c29c
Status: Started
Number of Bricks: 1 x 8 = 8
Transport-type: tcp
Bricks:
Brick1: jk:/home/jk/gluster/dsi129-brick1
Brick2: jk:/home/jk/gluster/dsi129-brick2
Brick3: jk:/home/jk/gluster/dsi129-brick3
Brick4: jk:/home/jk/gluster/dsi129-brick4
Brick5: jk:/home/jk/gluster/dsi129-brick5
Brick6: jk:/home/jk/gluster/dsi129-brick6
Brick7: jk:/home/jk/gluster/dsi129-brick7
Brick8: jk:/home/jk/gluster/dsi129-brick8
Options Reconfigured:
performance.readdir-ahead: on
Volume Name: dsi129-vol
Type : Disperse
Volume ID: 3537353c-f8ad-495e-bb17-0ddee4c2c29c
Status: Started
Number of Bricks: 1 x 8 = 8
Transport-type: tcp
Bricks:
Brick1: jk:/home/jk/gluster/dsi129-brick1
Brick2: jk:/home/jk/gluster/dsi129-brick2
Brick3: jk:/home/jk/gluster/dsi129-brick3
Brick4: jk:/home/jk/gluster/dsi129-brick4
Brick5: jk:/home/jk/gluster/dsi129-brick5
Brick6: jk:/home/jk/gluster/dsi129-brick6
Brick7: jk:/home/jk/gluster/dsi129-brick7
Brick8: jk:/home/jk/gluster/dsi129-brick8
Options Reconfigured:
performance.readdir-ahead: on
jk@jk:/var/log/glusterfs$ sudo gluster v status
Status of volume: dsi129-vol
Gluster process TCP Port RDMA Port Online Pid
------------------------------------------------------------------------------
Brick jk:/home/jk/gluster/dsi129-brick1 49162 0 Y 20339
Brick jk:/home/jk/gluster/dsi129-brick2 49163 0 Y 20357
Brick jk:/home/jk/gluster/dsi129-brick3 49189 0 Y 20375
Brick jk:/home/jk/gluster/dsi129-brick4 49190 0 Y 20393
Brick jk:/home/jk/gluster/dsi129-brick5 49191 0 Y 20411
Brick jk:/home/jk/gluster/dsi129-brick6 49192 0 Y 20429
Brick jk:/home/jk/gluster/dsi129-brick7 49193 0 Y 20448
Brick jk:/home/jk/gluster/dsi129-brick8 49194 0 Y 20466
NFS Server on localhost 2049 0 Y 20485
Task Status of Volume dsi129-vol
------------------------------------------------------------------------------
There are no active volume tasks
Status of volume: dsi129-vol
Gluster process TCP Port RDMA Port Online Pid
------------------------------------------------------------------------------
Brick jk:/home/jk/gluster/dsi129-brick1 49162 0 Y 20339
Brick jk:/home/jk/gluster/dsi129-brick2 49163 0 Y 20357
Brick jk:/home/jk/gluster/dsi129-brick3 49189 0 Y 20375
Brick jk:/home/jk/gluster/dsi129-brick4 49190 0 Y 20393
Brick jk:/home/jk/gluster/dsi129-brick5 49191 0 Y 20411
Brick jk:/home/jk/gluster/dsi129-brick6 49192 0 Y 20429
Brick jk:/home/jk/gluster/dsi129-brick7 49193 0 Y 20448
Brick jk:/home/jk/gluster/dsi129-brick8 49194 0 Y 20466
NFS Server on localhost 2049 0 Y 20485
Task Status of Volume dsi129-vol
------------------------------------------------------------------------------
There are no active volume tasks
Attached the log
mount command ;
sudo mount -t glusterfs jk:/dsi129-vol /mnt/gluster/dsi
Best Regards
JK
On Fri, Aug 5, 2016 at 5:18 PM, Ashish Pandey <aspandey@xxxxxxxxxx> wrote:
Please provide the output of "gluster vol info" and "gluster vol status" of the concerned volume.Also, please provide mount logs present in /var/log/gluster with name <mount point>.logWhat command are you executing while mouting, please mention exact command.From: "jayakrishnan mm" <jayakrishnan.mm@xxxxxxxxx>
To: gluster-users@xxxxxxxxxxx
Sent: Friday, August 5, 2016 1:50:33 PM
Subject: [Gluster-users] Unable to mount (glusterfs-fuse: 2: LOOKUP() error)_______________________________________________JKBest regardsAny clues ? How to proceed ?Vol status says , all bricks are online. But still unable to mount due to below error .Volume info says, vol is started.Glusterfs Ver 3.7.6Dispese vol[2016-08-05 07:33:37.192970] W [fuse-bridge.c:758:fuse_attr_cbk] 0-glusterfs-fuse: 2: LOOKUP() / => -1 (Transport endpoint is not connected).
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users