Re: [Gluster-devel] [Gluster-users] Replica 3 - how to replace failed node (peer)

2019-04-10 Thread Karthik Subrahmanya
On Thu, Apr 11, 2019 at 10:23 AM Karthik Subrahmanya wrote: > Hi Strahil, > > Can you give us some more insights on > - the volume configuration you were using? > - why you wanted to replace your brick? > - which brick(s) you tried replacing? > - if you remember the commands/steps that you follow

Re: [Gluster-devel] [Gluster-users] Replica 3 - how to replace failed node (peer)

2019-04-10 Thread Karthik Subrahmanya
Hi Strahil, Can you give us some more insights on - the volume configuration you were using? - why you wanted to replace your brick? - which brick(s) you tried replacing? - what problem(s) did you face? Regards, Karthik On Thu, Apr 11, 2019 at 10:14 AM Strahil wrote: > Hi Karthnik, > I used on

Re: [Gluster-devel] [Gluster-users] Replica 3 - how to replace failed node (peer)

2019-04-10 Thread Karthik Subrahmanya
Hi Strahil, Thank you for sharing your experience with reset-brick option. Since he is using the gluster version 3.7.6, we do not have the reset-brick [1] option implemented there. It is introduced in 3.9.0. He has to go with replace-brick with the force option if he wants to use the same path & n

Re: [Gluster-devel] test failure reports for last 15 days

2019-04-10 Thread FNU Raghavendra Manjunath
On Wed, Apr 10, 2019 at 9:59 AM Atin Mukherjee wrote: > And now for last 15 days: > > https://fstat.gluster.org/summary?start_date=2019-03-25&end_date=2019-04-10 > > ./tests/bitrot/bug-1373520.t 18 ==> Fixed through > https://review.gluster.org/#/c/glusterfs/+/22481/, I don't see this > fail

Re: [Gluster-devel] test failure reports for last 15 days

2019-04-10 Thread Xavi Hernandez
On Wed, Apr 10, 2019 at 4:01 PM Atin Mukherjee wrote: > And now for last 15 days: > > https://fstat.gluster.org/summary?start_date=2019-03-25&end_date=2019-04-10 > > ./tests/bitrot/bug-1373520.t 18 ==> Fixed through > https://review.gluster.org/#/c/glusterfs/+/22481/, I don't see this > fail

Re: [Gluster-devel] Gluster version EOL date

2019-04-10 Thread David Spisla
Hello Abhisek, take a look on this: https://lists.gluster.org/pipermail/announce/2018-July/000103.html and this https://www.gluster.org/release-schedule/ Gluster 5.5 is a patch release. Gluster 5.x will be spported until v8.0 Regards David Spisla David Spisla Software Engineer david.spi..

Re: [Gluster-devel] [Gluster-users] Proposal: Changes in Gluster Community meetings

2019-04-10 Thread Darrell Budic
As a user, I’d like to visit more of these, but the time slot is my 3AM. Any possibility for a rolling schedule (move meeting +6 hours each week with rolling attendance from maintainers?) or an occasional regional meeting 12 hours opposed to the one you’re proposing? -Darrell > On Mar 25, 20

Re: [Gluster-devel] test failure reports for last 15 days

2019-04-10 Thread Amar Tumballi Suryanarayan
Thanks for the summary Atin. On Wed, Apr 10, 2019 at 7:30 PM Atin Mukherjee wrote: > And now for last 15 days: > > https://fstat.gluster.org/summary?start_date=2019-03-25&end_date=2019-04-10 > > ./tests/bitrot/bug-1373520.t 18 ==> Fixed through > https://review.gluster.org/#/c/glusterfs/+/2

[Gluster-devel] test failure reports for last 15 days

2019-04-10 Thread Atin Mukherjee
And now for last 15 days: https://fstat.gluster.org/summary?start_date=2019-03-25&end_date=2019-04-10 ./tests/bitrot/bug-1373520.t 18 ==> Fixed through https://review.gluster.org/#/c/glusterfs/+/22481/, I don't see this failing in brick mux post 5th April ./tests/bugs/ec/bug-1236065.t 17

Re: [Gluster-devel] [Gluster-users] [External] Replica 3 - how to replace failed node (peer)

2019-04-10 Thread Karthik Subrahmanya
Hi Martin, The reset-brick command is introduced in 3.9.0 and not present in 3.7.6. You can try using the same replace-brick command with the force option even if you want to use the same name for the brick being replaced. 3.7.6 is EOLed long back and glusterfs-6 is the latest version with lots of

Re: [Gluster-devel] SHD crash in https://build.gluster.org/job/centos7-regression/5510/consoleFull

2019-04-10 Thread Atin Mukherjee
Rafi mentioned to me earlier that this will be fixed through https://review.gluster.org/22468 . This crash is more often seen in the nightly regression these days. Patch needs review and I'd request the respective maintainers to take a look at it. On Wed, Apr 10, 2019 at 5:08 PM Nithya Balachandra

[Gluster-devel] SHD crash in https://build.gluster.org/job/centos7-regression/5510/consoleFull

2019-04-10 Thread Nithya Balachandran
Hi, My patch is unlikely to have caused this as the changes are only in dht. Can someone take a look? Thanks, Nithya ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-users] Replica 3 - how to replace failed node (peer)

2019-04-10 Thread Karthik Subrahmanya
Hi Martin, After you add the new disks and creating raid array, you can run the following command to replace the old brick with new one: - If you are going to use a different name to the new brick you can run gluster volume replace-brickcommit force - If you are planning to use the same name

Re: [Gluster-devel] [Gluster-users] Replica 3 - how to replace failed node (peer)

2019-04-10 Thread RAFI KC
reset brick is another way of replacing a brick. this usually helpful, when you want to replace the brick with same name. You can find the documentation here https://docs.gluster.org/en/latest/release-notes/3.9.0/#introducing-reset-brick-command. In your case, I think you can use replace brick

Re: [Gluster-devel] [Gluster-users] Replica 3 - how to replace failed node (peer)

2019-04-10 Thread David Spisla
Hello Martin, look here: https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.4/pdf/administration_guide/Red_Hat_Gluster_Storage-3.4-Administration_Guide-en-US.pdf on page 324. There is a manual how to replace a brick in case of a hardware failure Regards David Spisla Am Mi.,