Hi Ashish,
sure, no problem! We are a little bit worried, but we can wait :-)
Thank you very much for your support and your availability.
Regards,
Mauro
> Il giorno 26 set 2018, alle ore 19:33, Ashish Pandey ha
> scritto:
>
> Hi Mauro,
>
> Yes, I can provide you step by step procedure to c
Hi Mauro,
Yes, I can provide you step by step procedure to correct it.
Is it fine If i provide you the steps tomorrow as it is quite late over here
and I don't want to miss anything in hurry?
---
Ashish
- Original Message -
From: "Mauro Tridici"
To: "Ashish Pandey"
Cc: "gluste
The Gluster community is pleased to announce the release of Gluster
4.1.5 (packages available at [1]).
Release notes for the release can be found at [2].
Major changes, features and limitations addressed in this release:
- Release 4.1.0 notes incorrectly reported that all python code in
Gluster
Hi Mauro,
rebalance and brick logs should be the first thing we should go through.
There is a procedure to correct the configuration/setup but the situation you
are in is difficult to follow that procedure.
You should have added the bricks hosted on s04-stg , s05-stg and s06-stg the
same way
Dear Ashish,
thank you for you answer.
I could provide you the entire log file related to glusterd, glusterfsd and
rebalance.
Please, could you indicate which one you need first?
Yes, we added the last 36 bricks after creating vol. Is there a procedure to
correct this error? Is it still possib
I think we don't have enough logs to debug this so I would suggest you to
provide more logs/info.
I have also observed that the configuration and setup of your volume is not
very efficient.
For example:
Brick37: s04-stg:/gluster/mnt1/brick
Brick38: s04-stg:/gluster/mnt2/brick
Brick39: s04-
Dear All, Dear Nithya,
after upgrading from 3.10.5 version to 3.12.14, I tried to start a rebalance
process to distribute data across the bricks, but something goes wrong.
Rebalance failed on different nodes and the time value needed to complete the
procedure seems to be very high.
[root@s01 ~]
On Tue, Sep 25, 2018 at 3:38 PM ABHISHEK PALIWAL
wrote:
> Hi Pranith,
>
> I have some questions if you can answer them:
>
>
> What in LIBC exit() routine has resulted in SIGSEGV in this case ?
>
As per the stack trace you provided it is _IO_unbuffer_all():
(gdb) bt
#0 0x3fffad4463b0 in _IO_u
