Adding brick volume to gluster fails

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












I created a 2TB volume to increase space on home directory.



I created the partition:



$ parted /dev/xvdb mklabel gpt
$ parted -s /dev/xvdb mkpart primary ext4 1 100%


Formatted the partition:



$ mkfs.ext4 -I 512 /dev/xvdb1


Added the entry to /etc/fstab



/dev/xvdb /export/home/brick3 ext4 defaults 0 0


Created the mountpoint:



$ mkdir -p /export/home/brick3
$ chmod 0755 /export/home/brick3


Mounted the partition:



$ mount /export/home/brick3
$ mkdir /export/home/brick3/home
$ chmod 0775 /export/home/brick3/home


once I tried to add the new brick to volume thats where I get an error.



$ gluster volume add-brick home <hostname>:/export/home/brick3/home
volume add-brick: failed Incorrect number of bricks supplied 1 with count 2



linux fdisk parted volume glusterfs




share|improve this question





















  • What's the output of the home volume look like? gluster volume info?
    – slm♦
    Jul 12 at 2:34










  • /dev/xvdca1 992G 843G 99G 90% /export/home/brick1 /dev/xvdcn1 992G 82G 859G 9% /export/home/brick2 /dev/xvdcp1 1.8T 68M 1.8T 1% /export/home/brick3
    – Mervyn Clarke
    Jul 16 at 18:39











  • Please add this to your Q.
    – slm♦
    Jul 16 at 18:47










  • I am adding all three after gluster volume add-brick... ?
    – Mervyn Clarke
    Jul 16 at 19:01










  • You need to add the number of replicas to that
    – slm♦
    Jul 16 at 19:11














up vote
1
down vote

favorite












I created a 2TB volume to increase space on home directory.



I created the partition:



$ parted /dev/xvdb mklabel gpt
$ parted -s /dev/xvdb mkpart primary ext4 1 100%


Formatted the partition:



$ mkfs.ext4 -I 512 /dev/xvdb1


Added the entry to /etc/fstab



/dev/xvdb /export/home/brick3 ext4 defaults 0 0


Created the mountpoint:



$ mkdir -p /export/home/brick3
$ chmod 0755 /export/home/brick3


Mounted the partition:



$ mount /export/home/brick3
$ mkdir /export/home/brick3/home
$ chmod 0775 /export/home/brick3/home


once I tried to add the new brick to volume thats where I get an error.



$ gluster volume add-brick home <hostname>:/export/home/brick3/home
volume add-brick: failed Incorrect number of bricks supplied 1 with count 2



linux fdisk parted volume glusterfs




share|improve this question





















  • What's the output of the home volume look like? gluster volume info?
    – slm♦
    Jul 12 at 2:34










  • /dev/xvdca1 992G 843G 99G 90% /export/home/brick1 /dev/xvdcn1 992G 82G 859G 9% /export/home/brick2 /dev/xvdcp1 1.8T 68M 1.8T 1% /export/home/brick3
    – Mervyn Clarke
    Jul 16 at 18:39











  • Please add this to your Q.
    – slm♦
    Jul 16 at 18:47










  • I am adding all three after gluster volume add-brick... ?
    – Mervyn Clarke
    Jul 16 at 19:01










  • You need to add the number of replicas to that
    – slm♦
    Jul 16 at 19:11












up vote
1
down vote

favorite









up vote
1
down vote

favorite











I created a 2TB volume to increase space on home directory.



I created the partition:



$ parted /dev/xvdb mklabel gpt
$ parted -s /dev/xvdb mkpart primary ext4 1 100%


Formatted the partition:



$ mkfs.ext4 -I 512 /dev/xvdb1


Added the entry to /etc/fstab



/dev/xvdb /export/home/brick3 ext4 defaults 0 0


Created the mountpoint:



$ mkdir -p /export/home/brick3
$ chmod 0755 /export/home/brick3


Mounted the partition:



$ mount /export/home/brick3
$ mkdir /export/home/brick3/home
$ chmod 0775 /export/home/brick3/home


once I tried to add the new brick to volume thats where I get an error.



$ gluster volume add-brick home <hostname>:/export/home/brick3/home
volume add-brick: failed Incorrect number of bricks supplied 1 with count 2



linux fdisk parted volume glusterfs




share|improve this question













I created a 2TB volume to increase space on home directory.



I created the partition:



$ parted /dev/xvdb mklabel gpt
$ parted -s /dev/xvdb mkpart primary ext4 1 100%


Formatted the partition:



$ mkfs.ext4 -I 512 /dev/xvdb1


Added the entry to /etc/fstab



/dev/xvdb /export/home/brick3 ext4 defaults 0 0


Created the mountpoint:



$ mkdir -p /export/home/brick3
$ chmod 0755 /export/home/brick3


Mounted the partition:



$ mount /export/home/brick3
$ mkdir /export/home/brick3/home
$ chmod 0775 /export/home/brick3/home


once I tried to add the new brick to volume thats where I get an error.



$ gluster volume add-brick home <hostname>:/export/home/brick3/home
volume add-brick: failed Incorrect number of bricks supplied 1 with count 2




linux fdisk parted volume glusterfs





share|improve this question












share|improve this question




share|improve this question








edited Jul 12 at 2:33









slm♦

233k65479651




233k65479651









asked Jul 11 at 14:37









Mervyn Clarke

184




184











  • What's the output of the home volume look like? gluster volume info?
    – slm♦
    Jul 12 at 2:34










  • /dev/xvdca1 992G 843G 99G 90% /export/home/brick1 /dev/xvdcn1 992G 82G 859G 9% /export/home/brick2 /dev/xvdcp1 1.8T 68M 1.8T 1% /export/home/brick3
    – Mervyn Clarke
    Jul 16 at 18:39











  • Please add this to your Q.
    – slm♦
    Jul 16 at 18:47










  • I am adding all three after gluster volume add-brick... ?
    – Mervyn Clarke
    Jul 16 at 19:01










  • You need to add the number of replicas to that
    – slm♦
    Jul 16 at 19:11
















  • What's the output of the home volume look like? gluster volume info?
    – slm♦
    Jul 12 at 2:34










  • /dev/xvdca1 992G 843G 99G 90% /export/home/brick1 /dev/xvdcn1 992G 82G 859G 9% /export/home/brick2 /dev/xvdcp1 1.8T 68M 1.8T 1% /export/home/brick3
    – Mervyn Clarke
    Jul 16 at 18:39











  • Please add this to your Q.
    – slm♦
    Jul 16 at 18:47










  • I am adding all three after gluster volume add-brick... ?
    – Mervyn Clarke
    Jul 16 at 19:01










  • You need to add the number of replicas to that
    – slm♦
    Jul 16 at 19:11















What's the output of the home volume look like? gluster volume info?
– slm♦
Jul 12 at 2:34




What's the output of the home volume look like? gluster volume info?
– slm♦
Jul 12 at 2:34












/dev/xvdca1 992G 843G 99G 90% /export/home/brick1 /dev/xvdcn1 992G 82G 859G 9% /export/home/brick2 /dev/xvdcp1 1.8T 68M 1.8T 1% /export/home/brick3
– Mervyn Clarke
Jul 16 at 18:39





/dev/xvdca1 992G 843G 99G 90% /export/home/brick1 /dev/xvdcn1 992G 82G 859G 9% /export/home/brick2 /dev/xvdcp1 1.8T 68M 1.8T 1% /export/home/brick3
– Mervyn Clarke
Jul 16 at 18:39













Please add this to your Q.
– slm♦
Jul 16 at 18:47




Please add this to your Q.
– slm♦
Jul 16 at 18:47












I am adding all three after gluster volume add-brick... ?
– Mervyn Clarke
Jul 16 at 19:01




I am adding all three after gluster volume add-brick... ?
– Mervyn Clarke
Jul 16 at 19:01












You need to add the number of replicas to that
– slm♦
Jul 16 at 19:11




You need to add the number of replicas to that
– slm♦
Jul 16 at 19:11










1 Answer
1






active

oldest

votes

















up vote
0
down vote













You need to include the replica $COUNT. This is a known issue when you have replicas enabled:




Current design constraints in replicate module doesn't allow for us to add individual bricks into an existing topology.




Scenario



You tried something like this:



$ gluster vol add-brick test-volume-replicated3 
 host:/rhss/bricks/brick1/test-volume-replicated3

volume add-brick: failed: Incorrect number of bricks supplied 1 with count 2


Your scenario is likely one where you have a number of replicas configured for your gluster volume because it was built like this originally:



$ gluster vol create test-volume-replicated3 replica 3 
 host1:/rhss/bricks/brick1/test-volume-replicated3 
 host2:/rhss/bricks/brick1/test-volume-replicated3 
 host3:/rhss/bricks/brick1/test-volume-replicated3
volume create: test-volume-replicated3: success: please start the volume to access data


And currently its topology is now like this:



$ gluster vol info test-volume-replicated3

Volume Name: test-volume-replicated3
Type: Replicate
Volume ID: 10b3d0e2-14a2-4ec3-a98c-9a3307f3fd8f
Status: Created
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: host1:/rhss/bricks/brick1/test-volume-replicated3
Brick2: host2:/rhss/bricks/brick1/test-volume-replicated3
Brick3: host3:/rhss/bricks/brick1/test-volume-replicated3


So to get your command to run you have to tell gluster your replica count when adding another brick:



$ gluster vol add-brick test-volume-replicated3 replica 3 
 host:/rhss/bricks/brick1/test-volume-replicated3 
 host:/rhss/bricks/brick2/test-volume-replicated3 
 host:/rhss/bricks/brick3/test-volume-replicated3


References



  • How to add a new brick to an existing replicated volume?





share|improve this answer





















    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    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',
    convertImagesToLinks: false,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );








     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f454707%2fadding-brick-volume-to-gluster-fails%23new-answer', 'question_page');

    );

    Post as a guest

















    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote













    You need to include the replica $COUNT. This is a known issue when you have replicas enabled:




    Current design constraints in replicate module doesn't allow for us to add individual bricks into an existing topology.




    Scenario



    You tried something like this:



    $ gluster vol add-brick test-volume-replicated3 
     host:/rhss/bricks/brick1/test-volume-replicated3

    volume add-brick: failed: Incorrect number of bricks supplied 1 with count 2


    Your scenario is likely one where you have a number of replicas configured for your gluster volume because it was built like this originally:



    $ gluster vol create test-volume-replicated3 replica 3 
     host1:/rhss/bricks/brick1/test-volume-replicated3 
     host2:/rhss/bricks/brick1/test-volume-replicated3 
     host3:/rhss/bricks/brick1/test-volume-replicated3
    volume create: test-volume-replicated3: success: please start the volume to access data


    And currently its topology is now like this:



    $ gluster vol info test-volume-replicated3

    Volume Name: test-volume-replicated3
    Type: Replicate
    Volume ID: 10b3d0e2-14a2-4ec3-a98c-9a3307f3fd8f
    Status: Created
    Number of Bricks: 1 x 3 = 3
    Transport-type: tcp
    Bricks:
    Brick1: host1:/rhss/bricks/brick1/test-volume-replicated3
    Brick2: host2:/rhss/bricks/brick1/test-volume-replicated3
    Brick3: host3:/rhss/bricks/brick1/test-volume-replicated3


    So to get your command to run you have to tell gluster your replica count when adding another brick:



    $ gluster vol add-brick test-volume-replicated3 replica 3 
     host:/rhss/bricks/brick1/test-volume-replicated3 
     host:/rhss/bricks/brick2/test-volume-replicated3 
     host:/rhss/bricks/brick3/test-volume-replicated3


    References



    • How to add a new brick to an existing replicated volume?





    share|improve this answer

























      up vote
      0
      down vote













      You need to include the replica $COUNT. This is a known issue when you have replicas enabled:




      Current design constraints in replicate module doesn't allow for us to add individual bricks into an existing topology.




      Scenario



      You tried something like this:



      $ gluster vol add-brick test-volume-replicated3 
       host:/rhss/bricks/brick1/test-volume-replicated3

      volume add-brick: failed: Incorrect number of bricks supplied 1 with count 2


      Your scenario is likely one where you have a number of replicas configured for your gluster volume because it was built like this originally:



      $ gluster vol create test-volume-replicated3 replica 3 
       host1:/rhss/bricks/brick1/test-volume-replicated3 
       host2:/rhss/bricks/brick1/test-volume-replicated3 
       host3:/rhss/bricks/brick1/test-volume-replicated3
      volume create: test-volume-replicated3: success: please start the volume to access data


      And currently its topology is now like this:



      $ gluster vol info test-volume-replicated3

      Volume Name: test-volume-replicated3
      Type: Replicate
      Volume ID: 10b3d0e2-14a2-4ec3-a98c-9a3307f3fd8f
      Status: Created
      Number of Bricks: 1 x 3 = 3
      Transport-type: tcp
      Bricks:
      Brick1: host1:/rhss/bricks/brick1/test-volume-replicated3
      Brick2: host2:/rhss/bricks/brick1/test-volume-replicated3
      Brick3: host3:/rhss/bricks/brick1/test-volume-replicated3


      So to get your command to run you have to tell gluster your replica count when adding another brick:



      $ gluster vol add-brick test-volume-replicated3 replica 3 
       host:/rhss/bricks/brick1/test-volume-replicated3 
       host:/rhss/bricks/brick2/test-volume-replicated3 
       host:/rhss/bricks/brick3/test-volume-replicated3


      References



      • How to add a new brick to an existing replicated volume?





      share|improve this answer























        up vote
        0
        down vote










        up vote
        0
        down vote









        You need to include the replica $COUNT. This is a known issue when you have replicas enabled:




        Current design constraints in replicate module doesn't allow for us to add individual bricks into an existing topology.




        Scenario



        You tried something like this:



        $ gluster vol add-brick test-volume-replicated3 
         host:/rhss/bricks/brick1/test-volume-replicated3

        volume add-brick: failed: Incorrect number of bricks supplied 1 with count 2


        Your scenario is likely one where you have a number of replicas configured for your gluster volume because it was built like this originally:



        $ gluster vol create test-volume-replicated3 replica 3 
         host1:/rhss/bricks/brick1/test-volume-replicated3 
         host2:/rhss/bricks/brick1/test-volume-replicated3 
         host3:/rhss/bricks/brick1/test-volume-replicated3
        volume create: test-volume-replicated3: success: please start the volume to access data


        And currently its topology is now like this:



        $ gluster vol info test-volume-replicated3

        Volume Name: test-volume-replicated3
        Type: Replicate
        Volume ID: 10b3d0e2-14a2-4ec3-a98c-9a3307f3fd8f
        Status: Created
        Number of Bricks: 1 x 3 = 3
        Transport-type: tcp
        Bricks:
        Brick1: host1:/rhss/bricks/brick1/test-volume-replicated3
        Brick2: host2:/rhss/bricks/brick1/test-volume-replicated3
        Brick3: host3:/rhss/bricks/brick1/test-volume-replicated3


        So to get your command to run you have to tell gluster your replica count when adding another brick:



        $ gluster vol add-brick test-volume-replicated3 replica 3 
         host:/rhss/bricks/brick1/test-volume-replicated3 
         host:/rhss/bricks/brick2/test-volume-replicated3 
         host:/rhss/bricks/brick3/test-volume-replicated3


        References



        • How to add a new brick to an existing replicated volume?





        share|improve this answer













        You need to include the replica $COUNT. This is a known issue when you have replicas enabled:




        Current design constraints in replicate module doesn't allow for us to add individual bricks into an existing topology.




        Scenario



        You tried something like this:



        $ gluster vol add-brick test-volume-replicated3 
         host:/rhss/bricks/brick1/test-volume-replicated3

        volume add-brick: failed: Incorrect number of bricks supplied 1 with count 2


        Your scenario is likely one where you have a number of replicas configured for your gluster volume because it was built like this originally:



        $ gluster vol create test-volume-replicated3 replica 3 
         host1:/rhss/bricks/brick1/test-volume-replicated3 
         host2:/rhss/bricks/brick1/test-volume-replicated3 
         host3:/rhss/bricks/brick1/test-volume-replicated3
        volume create: test-volume-replicated3: success: please start the volume to access data


        And currently its topology is now like this:



        $ gluster vol info test-volume-replicated3

        Volume Name: test-volume-replicated3
        Type: Replicate
        Volume ID: 10b3d0e2-14a2-4ec3-a98c-9a3307f3fd8f
        Status: Created
        Number of Bricks: 1 x 3 = 3
        Transport-type: tcp
        Bricks:
        Brick1: host1:/rhss/bricks/brick1/test-volume-replicated3
        Brick2: host2:/rhss/bricks/brick1/test-volume-replicated3
        Brick3: host3:/rhss/bricks/brick1/test-volume-replicated3


        So to get your command to run you have to tell gluster your replica count when adding another brick:



        $ gluster vol add-brick test-volume-replicated3 replica 3 
         host:/rhss/bricks/brick1/test-volume-replicated3 
         host:/rhss/bricks/brick2/test-volume-replicated3 
         host:/rhss/bricks/brick3/test-volume-replicated3


        References



        • How to add a new brick to an existing replicated volume?






        share|improve this answer













        share|improve this answer



        share|improve this answer











        answered Jul 12 at 2:41









        slm♦

        233k65479651




        233k65479651






















             

            draft saved


            draft discarded


























             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f454707%2fadding-brick-volume-to-gluster-fails%23new-answer', 'question_page');

            );

            Post as a guest
































































            -

            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Image
            Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Sep 26 at 0:12 ToanLuong 49 9 add a comment  |  up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Se
            Read more

            Bahrain

            Image
            For other uses, see Bahrain (disambiguation). Sovereign island state in the Persian Gulf Kingdom of Bahrain مملكة البحرين   (Arabic) Mamlakat al-Baḥrayn Flag Coat of arms Anthem:  نشيد البحرين الوطني Bahrainona Our Bahrain Location of   Bahrain    (circled in red) Capital and largest city Manama 26°13′N 50°35′E  /  26.217°N 50.583°E  / 26.217; 50.583 Official languages Arabic Ethnic groups (2010 [1] ) 50.7% Arab (46% Bahrani, 4.7% other Arabs) 45.5% Asian 1% European 1.2% Others Religion Islam Demonym(s) Bahraini Government Unitary constitutional monarchy • King Hamad bin Isa Al Khalifa • Crown Prince Salman bin Hamad bin Isa Al Khalifa • Prime Minister Khalifa bin Salman Al Khalifa Legislature National Assembly • Upper house Consultative Council • Lower house Council of Representatives Independence • Declared Independence [2] 14 August 1971 • from United Kingdom [1] 15 August 1971 • Admitted to the United Nations 21 September 1971 • Kingdom of Bahrain 14 February 2002
            Read more

            Postfix configuration issue with fips on centos 7; mailgun relay

            Image
            Clash Royale CLAN TAG #URR8PPP up vote 0 down vote favorite I am trying to setup postfix to relay all mail generated on the local machine via SMTP to a mailgun relay. I have used the mailgun relay before with success on an ubuntu server, but I am migrating to a Centos 7 server which I will be running in FIPS mode. There error log is below, slightly sanitized. I have a small enough network that I choose to have each machine reach out to mailgun individually (this the loopback-only, 127.0.0.0/8 restrictions) and no firewall open port allowing smtp in to the machine. I assume the FIPS mode (and with it disabling of MD5) is causing problems, but I don't know how to overcome it or if it is even possible for tls_fprint to use some supported hash such as sha256 or sha512. However, the relay=none is slightly concerning since I have relayhost set, but perhaps that is because the smtp process is failing? Any help would be appreciated! postconf -n: alias_database = hash:/etc/alia
            Read more