<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Fri, Sep 21, 2018 at 12:44 AM Chaloulos, Klearchos (Nokia - GR/Athens) <<a href="mailto:klearchos.chaloulos@nokia.com">klearchos.chaloulos@nokia.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<font face="Calibri" size="2"><span style="font-size:11pt">
<div>Hello,</div>
<div> </div>
<div>We are using glusterfs version 3.7.14, and have deployed the glusterfs servers in containers. We are trying to use the “gluster volume add-brick” command to extend a volume, but it fails:</div>
<div> </div>
<div><font face="Courier New">gluster volume add-brick oam replica 3 172.01.01.01:/mnt/bricks/oam force</font></div>
<div><font face="Courier New">volume add-brick: failed: Commit failed on 172.01.01.01. Please check log file for details.</font></div>
<div> </div>
<div>The logs show that it fails to mount /dev/fuse:</div>
<div> </div>
<div><font face="Courier New">[mount.c:341:gf_fuse_mount] 0-glusterfs-fuse: cannot open \/dev\/fuse (No such file or directory)</font></div>
<div><font face="Courier New">[glusterd-utils.c:11294:glusterd_handle_replicate_brick_ops] 0-management: mount command failed.</font></div>
<div><font face="Courier New">[MSGID: 106074] [glusterd-brick-ops.c:2372:glusterd_op_add_brick] 0-glusterd: Unable to add bricks</font></div>
<div><font face="Courier New">[MSGID: 106123] [glusterd-mgmt.c:294:gd_mgmt_v3_commit_fn] 0-management: Add-brick commit failed.</font></div>
<div> </div>
<div>Questions:</div>
<ol style="margin:0;padding-left:36pt;list-style-type:decimal">
<li>Why does it need /dev/fuse in order to add a brick?</li></ol></span></font></div></blockquote><div><br></div><div>/dev/fuse or the fuse kernel module is needed on a server that contains a brick as several features in gluster rely on mounting a native(fuse) client locally on the server. </div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><font face="Calibri" size="2"><span style="font-size:11pt"><ol style="margin:0;padding-left:36pt;list-style-type:decimal"><li>Is there a way to bypass the need for /dev/fuse in order to add the extra brick?</li></ol></span></font></div></blockquote><div><br></div><div>I don't think there is an easy way at the moment. Making the fuse kernel module available to the glusterfs installation in the container would be the preferred route as of now.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><font face="Calibri" size="2"><span style="font-size:11pt"><ol style="margin:0;padding-left:36pt;list-style-type:decimal"><li>Is this related to this issue: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1420027" target="_blank"><font color="#0563C1"><u>https://bugzilla.redhat.com/show_bug.cgi?id=1420027</u></font></a> ?</li></ol></span></font></div></blockquote><div><br></div><div>Yes, this is related to the issue reported in the bug. There is a fair amount of work needed to avoid dependency of the glusterfs server stack on a fuse mount.</div><div><br></div><div>Best Regards,</div><div>Vijay</div><div> <br></div></div></div>