GlusterFs - remove and Add brick is not possibleGluster: What's a Brick vs a NodeGlusterFS - 'Host not...

What is the wife of a henpecked husband called?

How to mitigate "bandwagon attacking" from players?

Could be quantum mechanics necessary to analyze some biology scenarios?

Eww, those bytes are gross

What can I substitute for soda pop in a sweet pork recipe?

Connecting top and bottom of adjacent circles

Where was Karl Mordo in Infinity War?

It took me a lot of time to make this, pls like. (YouTube Comments #1)

What is better: yes / no radio, or simple checkbox?

Table enclosed in curly brackets

What happens if a wizard reaches level 20 but has no 3rd-level spells that they can use with the Signature Spells feature?

How do you enable SQL Server 2019's result set caching?

Can I retract my name from an already published manuscript?

What to do when being responsible for data protection in your lab, yet advice is ignored?

How should I state my MS degree in my CV when it was in practice a joint-program?

Do any poskim exempt 13-20-year-olds from Mussaf?

Criticizing long fiction. How is it different from short?

Do objects in the public view need licencing?

Called into a meeting and told we are being made redundant (laid off) and "not to share outside". Can I tell my partner?

On what did Lego base the appearance of the new Hogwarts minifigs?

By American Standards

ip vs ifconfig commands pros and cons

Am I using the wrong word all along?

Meth dealer reference in Family Guy



GlusterFs - remove and Add brick is not possible


Gluster: What's a Brick vs a NodeGlusterFS - 'Host not connected' when creating a volume on VBox VMsHow to properly configure a 2 node glusterfs system?Can I do the GlusterFS setup with a LB or heartbeat service in SLES 12? If yes, How?GlusterFS rebalancing volume failedGlusterFS : When a node is down the second doesn't take overgluster operations hangs when one node failUnexplicable GlusterFS load and poor performanceGlusterfs 2x server issueglusterfs client mount point fails with 'Client quorum is not met'













0















I have a GlusterFS (3.12.1) cluster of 3 nodes.



Setp 1: removed a node (node2)



from node1



# gluster volume remove-brick swarm-data replica 2 node2:/glusterfs/swarm-data force  
# gluster peer detach node2


Setp 2: clear node



from node2



# rm -rf /glusterfs/swarm-data  
# mkdir /glusterfs/swarm-data


And maintenance job



Setp 3: re-add node



from node1



# gluster peer probe node2  
# gluster volume add-brick swarm-data replica 3 node2:/glusterfs/swarm-data force
volume add-brick: failed: Commit failed on node2. Please check log
file for details.


show logs :



failed to get the port number for remote subvolume. Please run 'gluster volume status' on server to see if brick process is running.
E [MSGID: 108006] [afr-common.c:5001:__afr_handle_child_down_event] 0-swarm-data-replicate-0: All subvolumes are down. Going offline until atleast one of them comes back up.


next:



# gluster volume status
Status of volume: swarm-data
Gluster process TCP Port RDMA Port Online Pid
------------------------------------------------------------------------------
Brick node1:/glusterfs/swarm
-data 49152 0 Y 31216
Brick node3:/glusterfs/swarm
-data 49152 0 Y 2373
Brick node2:/glusterfs/swarm
-data N/A N/A N N/A
Self-heal Daemon on localhost N/A N/A Y 27293
Self-heal Daemon on node3 N/A N/A Y 20268
Self-heal Daemon on node2 N/A N/A Y 7568

Task Status of Volume swarm-data
------------------------------------------------------------------------------
There are no active volume tasks


=> TCP Port : N/A for Node2 !!



Next:



# gluster volume info swarm-data

Volume Name: swarm-data
Type: Replicate
Volume ID: 0edd8275-8d39-4e95-abc8-9f028c2098a7
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: node1:/glusterfs/swarm-data
Brick2: node3:/glusterfs/swarm-data
Brick3: node2:/glusterfs/swarm-data
Options Reconfigured:
auth.allow: 127.0.0.1
transport.address-family: inet
nfs.disable: on


Node2 is here!
but no data sync



nodes 1 and 3 have port 49152 listening but not node 2 with:



netstat -an | grep LISTEN


Can you help me ?










share|improve this question














bumped to the homepage by Community 13 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.




















    0















    I have a GlusterFS (3.12.1) cluster of 3 nodes.



    Setp 1: removed a node (node2)



    from node1



    # gluster volume remove-brick swarm-data replica 2 node2:/glusterfs/swarm-data force  
    # gluster peer detach node2


    Setp 2: clear node



    from node2



    # rm -rf /glusterfs/swarm-data  
    # mkdir /glusterfs/swarm-data


    And maintenance job



    Setp 3: re-add node



    from node1



    # gluster peer probe node2  
    # gluster volume add-brick swarm-data replica 3 node2:/glusterfs/swarm-data force
    volume add-brick: failed: Commit failed on node2. Please check log
    file for details.


    show logs :



    failed to get the port number for remote subvolume. Please run 'gluster volume status' on server to see if brick process is running.
    E [MSGID: 108006] [afr-common.c:5001:__afr_handle_child_down_event] 0-swarm-data-replicate-0: All subvolumes are down. Going offline until atleast one of them comes back up.


    next:



    # gluster volume status
    Status of volume: swarm-data
    Gluster process TCP Port RDMA Port Online Pid
    ------------------------------------------------------------------------------
    Brick node1:/glusterfs/swarm
    -data 49152 0 Y 31216
    Brick node3:/glusterfs/swarm
    -data 49152 0 Y 2373
    Brick node2:/glusterfs/swarm
    -data N/A N/A N N/A
    Self-heal Daemon on localhost N/A N/A Y 27293
    Self-heal Daemon on node3 N/A N/A Y 20268
    Self-heal Daemon on node2 N/A N/A Y 7568

    Task Status of Volume swarm-data
    ------------------------------------------------------------------------------
    There are no active volume tasks


    => TCP Port : N/A for Node2 !!



    Next:



    # gluster volume info swarm-data

    Volume Name: swarm-data
    Type: Replicate
    Volume ID: 0edd8275-8d39-4e95-abc8-9f028c2098a7
    Status: Started
    Snapshot Count: 0
    Number of Bricks: 1 x 3 = 3
    Transport-type: tcp
    Bricks:
    Brick1: node1:/glusterfs/swarm-data
    Brick2: node3:/glusterfs/swarm-data
    Brick3: node2:/glusterfs/swarm-data
    Options Reconfigured:
    auth.allow: 127.0.0.1
    transport.address-family: inet
    nfs.disable: on


    Node2 is here!
    but no data sync



    nodes 1 and 3 have port 49152 listening but not node 2 with:



    netstat -an | grep LISTEN


    Can you help me ?










    share|improve this question














    bumped to the homepage by Community 13 hours ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      0












      0








      0








      I have a GlusterFS (3.12.1) cluster of 3 nodes.



      Setp 1: removed a node (node2)



      from node1



      # gluster volume remove-brick swarm-data replica 2 node2:/glusterfs/swarm-data force  
      # gluster peer detach node2


      Setp 2: clear node



      from node2



      # rm -rf /glusterfs/swarm-data  
      # mkdir /glusterfs/swarm-data


      And maintenance job



      Setp 3: re-add node



      from node1



      # gluster peer probe node2  
      # gluster volume add-brick swarm-data replica 3 node2:/glusterfs/swarm-data force
      volume add-brick: failed: Commit failed on node2. Please check log
      file for details.


      show logs :



      failed to get the port number for remote subvolume. Please run 'gluster volume status' on server to see if brick process is running.
      E [MSGID: 108006] [afr-common.c:5001:__afr_handle_child_down_event] 0-swarm-data-replicate-0: All subvolumes are down. Going offline until atleast one of them comes back up.


      next:



      # gluster volume status
      Status of volume: swarm-data
      Gluster process TCP Port RDMA Port Online Pid
      ------------------------------------------------------------------------------
      Brick node1:/glusterfs/swarm
      -data 49152 0 Y 31216
      Brick node3:/glusterfs/swarm
      -data 49152 0 Y 2373
      Brick node2:/glusterfs/swarm
      -data N/A N/A N N/A
      Self-heal Daemon on localhost N/A N/A Y 27293
      Self-heal Daemon on node3 N/A N/A Y 20268
      Self-heal Daemon on node2 N/A N/A Y 7568

      Task Status of Volume swarm-data
      ------------------------------------------------------------------------------
      There are no active volume tasks


      => TCP Port : N/A for Node2 !!



      Next:



      # gluster volume info swarm-data

      Volume Name: swarm-data
      Type: Replicate
      Volume ID: 0edd8275-8d39-4e95-abc8-9f028c2098a7
      Status: Started
      Snapshot Count: 0
      Number of Bricks: 1 x 3 = 3
      Transport-type: tcp
      Bricks:
      Brick1: node1:/glusterfs/swarm-data
      Brick2: node3:/glusterfs/swarm-data
      Brick3: node2:/glusterfs/swarm-data
      Options Reconfigured:
      auth.allow: 127.0.0.1
      transport.address-family: inet
      nfs.disable: on


      Node2 is here!
      but no data sync



      nodes 1 and 3 have port 49152 listening but not node 2 with:



      netstat -an | grep LISTEN


      Can you help me ?










      share|improve this question














      I have a GlusterFS (3.12.1) cluster of 3 nodes.



      Setp 1: removed a node (node2)



      from node1



      # gluster volume remove-brick swarm-data replica 2 node2:/glusterfs/swarm-data force  
      # gluster peer detach node2


      Setp 2: clear node



      from node2



      # rm -rf /glusterfs/swarm-data  
      # mkdir /glusterfs/swarm-data


      And maintenance job



      Setp 3: re-add node



      from node1



      # gluster peer probe node2  
      # gluster volume add-brick swarm-data replica 3 node2:/glusterfs/swarm-data force
      volume add-brick: failed: Commit failed on node2. Please check log
      file for details.


      show logs :



      failed to get the port number for remote subvolume. Please run 'gluster volume status' on server to see if brick process is running.
      E [MSGID: 108006] [afr-common.c:5001:__afr_handle_child_down_event] 0-swarm-data-replicate-0: All subvolumes are down. Going offline until atleast one of them comes back up.


      next:



      # gluster volume status
      Status of volume: swarm-data
      Gluster process TCP Port RDMA Port Online Pid
      ------------------------------------------------------------------------------
      Brick node1:/glusterfs/swarm
      -data 49152 0 Y 31216
      Brick node3:/glusterfs/swarm
      -data 49152 0 Y 2373
      Brick node2:/glusterfs/swarm
      -data N/A N/A N N/A
      Self-heal Daemon on localhost N/A N/A Y 27293
      Self-heal Daemon on node3 N/A N/A Y 20268
      Self-heal Daemon on node2 N/A N/A Y 7568

      Task Status of Volume swarm-data
      ------------------------------------------------------------------------------
      There are no active volume tasks


      => TCP Port : N/A for Node2 !!



      Next:



      # gluster volume info swarm-data

      Volume Name: swarm-data
      Type: Replicate
      Volume ID: 0edd8275-8d39-4e95-abc8-9f028c2098a7
      Status: Started
      Snapshot Count: 0
      Number of Bricks: 1 x 3 = 3
      Transport-type: tcp
      Bricks:
      Brick1: node1:/glusterfs/swarm-data
      Brick2: node3:/glusterfs/swarm-data
      Brick3: node2:/glusterfs/swarm-data
      Options Reconfigured:
      auth.allow: 127.0.0.1
      transport.address-family: inet
      nfs.disable: on


      Node2 is here!
      but no data sync



      nodes 1 and 3 have port 49152 listening but not node 2 with:



      netstat -an | grep LISTEN


      Can you help me ?







      glusterfs






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 26 '17 at 15:31









      user2452092user2452092

      11




      11





      bumped to the homepage by Community 13 hours ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 13 hours ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          2 Answers
          2






          active

          oldest

          votes


















          0














          Check the resolution name ( DNS or hosts file ).
          Check the glusterd services on node2 is started or not.
          If glusterd not start post the log.






          share|improve this answer
























          • Thank you for your answer. It's ok, I can create another volume on my 3 nodes. But still not for my first volume. I did not try to stop the volume before adding a node (I'm on a server in production).

            – user2452092
            Nov 28 '17 at 12:22











          • Yes. Glustrfs is ha and fail over storage system: you do not stop services. If you create a new volume you must migrates all data from old volume to new volume. Another trick try to check var/lib/gluster if you have old config.

            – Alessandro Secchi
            Nov 28 '17 at 12:47



















          0














          I have occasionally encountered this situation, too.
          You could try to restart GlusterFS service later and check it again:



          systemctl restart glusterd
          gluster volume status





          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "2"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f885217%2fglusterfs-remove-and-add-brick-is-not-possible%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Check the resolution name ( DNS or hosts file ).
            Check the glusterd services on node2 is started or not.
            If glusterd not start post the log.






            share|improve this answer
























            • Thank you for your answer. It's ok, I can create another volume on my 3 nodes. But still not for my first volume. I did not try to stop the volume before adding a node (I'm on a server in production).

              – user2452092
              Nov 28 '17 at 12:22











            • Yes. Glustrfs is ha and fail over storage system: you do not stop services. If you create a new volume you must migrates all data from old volume to new volume. Another trick try to check var/lib/gluster if you have old config.

              – Alessandro Secchi
              Nov 28 '17 at 12:47
















            0














            Check the resolution name ( DNS or hosts file ).
            Check the glusterd services on node2 is started or not.
            If glusterd not start post the log.






            share|improve this answer
























            • Thank you for your answer. It's ok, I can create another volume on my 3 nodes. But still not for my first volume. I did not try to stop the volume before adding a node (I'm on a server in production).

              – user2452092
              Nov 28 '17 at 12:22











            • Yes. Glustrfs is ha and fail over storage system: you do not stop services. If you create a new volume you must migrates all data from old volume to new volume. Another trick try to check var/lib/gluster if you have old config.

              – Alessandro Secchi
              Nov 28 '17 at 12:47














            0












            0








            0







            Check the resolution name ( DNS or hosts file ).
            Check the glusterd services on node2 is started or not.
            If glusterd not start post the log.






            share|improve this answer













            Check the resolution name ( DNS or hosts file ).
            Check the glusterd services on node2 is started or not.
            If glusterd not start post the log.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Nov 28 '17 at 10:49









            Alessandro SecchiAlessandro Secchi

            3013




            3013













            • Thank you for your answer. It's ok, I can create another volume on my 3 nodes. But still not for my first volume. I did not try to stop the volume before adding a node (I'm on a server in production).

              – user2452092
              Nov 28 '17 at 12:22











            • Yes. Glustrfs is ha and fail over storage system: you do not stop services. If you create a new volume you must migrates all data from old volume to new volume. Another trick try to check var/lib/gluster if you have old config.

              – Alessandro Secchi
              Nov 28 '17 at 12:47



















            • Thank you for your answer. It's ok, I can create another volume on my 3 nodes. But still not for my first volume. I did not try to stop the volume before adding a node (I'm on a server in production).

              – user2452092
              Nov 28 '17 at 12:22











            • Yes. Glustrfs is ha and fail over storage system: you do not stop services. If you create a new volume you must migrates all data from old volume to new volume. Another trick try to check var/lib/gluster if you have old config.

              – Alessandro Secchi
              Nov 28 '17 at 12:47

















            Thank you for your answer. It's ok, I can create another volume on my 3 nodes. But still not for my first volume. I did not try to stop the volume before adding a node (I'm on a server in production).

            – user2452092
            Nov 28 '17 at 12:22





            Thank you for your answer. It's ok, I can create another volume on my 3 nodes. But still not for my first volume. I did not try to stop the volume before adding a node (I'm on a server in production).

            – user2452092
            Nov 28 '17 at 12:22













            Yes. Glustrfs is ha and fail over storage system: you do not stop services. If you create a new volume you must migrates all data from old volume to new volume. Another trick try to check var/lib/gluster if you have old config.

            – Alessandro Secchi
            Nov 28 '17 at 12:47





            Yes. Glustrfs is ha and fail over storage system: you do not stop services. If you create a new volume you must migrates all data from old volume to new volume. Another trick try to check var/lib/gluster if you have old config.

            – Alessandro Secchi
            Nov 28 '17 at 12:47













            0














            I have occasionally encountered this situation, too.
            You could try to restart GlusterFS service later and check it again:



            systemctl restart glusterd
            gluster volume status





            share|improve this answer




























              0














              I have occasionally encountered this situation, too.
              You could try to restart GlusterFS service later and check it again:



              systemctl restart glusterd
              gluster volume status





              share|improve this answer


























                0












                0








                0







                I have occasionally encountered this situation, too.
                You could try to restart GlusterFS service later and check it again:



                systemctl restart glusterd
                gluster volume status





                share|improve this answer













                I have occasionally encountered this situation, too.
                You could try to restart GlusterFS service later and check it again:



                systemctl restart glusterd
                gluster volume status






                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jun 5 '18 at 7:40









                i_chipsi_chips

                1




                1






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Server Fault!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f885217%2fglusterfs-remove-and-add-brick-is-not-possible%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    117736 Шеррод Примітки | Див. також | Посилання | Навігаційне...

                    As a Security Precaution, the user account has been locked The Next CEO of Stack OverflowMS...

                    Маріан Котлеба Зміст Життєпис | Політичні погляди |...