Re: [Gluster-users] [Gluster-devel] Version uplift query

2019-02-27 Thread Milind Changire
you might want to check what build.log says ... especially at the very bottom Here's a hint from StackExhange . On Thu, Feb 28, 2019 at 12:42 PM ABHISHEK PALIWAL wrote: > I am trying to build Gluster5.4 but getting below

Re: [Gluster-users] Version uplift query

2019-02-27 Thread ABHISHEK PALIWAL
I am trying to build Gluster5.4 but getting below error at the time of configure conftest.c:11:28: fatal error: ac_nonexistent.h: No such file or directory Could you please help me what is the reason of the above error. Regards, Abhishek On Wed, Feb 27, 2019 at 8:42 PM Amar Tumballi

Re: [Gluster-users] Version uplift query

2019-02-27 Thread Amudhan P
Hi Poornima, Instead of killing process stopping volume followed by stopping service in nodes and update glusterfs. can't we follow the above step? regards Amudhan On Thu, Feb 28, 2019 at 8:16 AM Poornima Gurusiddaiah wrote: > > > On Wed, Feb 27, 2019, 11:52 PM Ingo Fischer wrote: > >> Hi

Re: [Gluster-users] Version uplift query

2019-02-27 Thread Poornima Gurusiddaiah
On Wed, Feb 27, 2019, 11:52 PM Ingo Fischer wrote: > Hi Amar, > > sorry to jump into this thread with an connected question. > > When installing via "apt-get" and so using debian packages and also > systemd to start/stop glusterd is the online upgrade process from > 3.x/4.x to 5.x still needed

Re: [Gluster-users] Fwd: Added bricks with wrong name and now need to remove them without destroying volume.

2019-02-27 Thread Jim Kinney
It sounds like new bricks were added and they mounted over the top of existing bricks. gluster volume status detail This will give the data you need to find where the real files are. You can look in those to see the data should be intact. Stopping the gluster volume is a good first step. Then as

Re: [Gluster-users] Fwd: Added bricks with wrong name and now need to remove them without destroying volume.

2019-02-27 Thread Tami Greene
That makes sense. System is made of four data arrays with a hardware RAID 6 and then the distributed volume on top. I honestly don't know how that works, but the previous administrator said we had redundancy. I'm hoping there is a way to bypass the safeguard of migrating data when removing a

Re: [Gluster-users] Fwd: Added bricks with wrong name and now need to remove them without destroying volume.

2019-02-27 Thread Jim Kinney
Keep in mind that gluster is a metadata process. It doesn't really touch the actual volume files. The exception is the .glusterfs and .trashcan folders in the very top directory of the gluster volume. When you create a gluster volume from brick, it doesn't format the filesystem. It uses what's

[Gluster-users] Fwd: Added bricks with wrong name and now need to remove them without destroying volume.

2019-02-27 Thread Tami Greene
I sent this and realized I hadn't registered. My apologies for the duplication Subject: Added bricks with wrong name and now need to remove them without destroying volume. To: Yes, I broke it. Now I need help fixing it. I have an existing Gluster Volume, spread over 16 bricks and 4

[Gluster-users] Added bricks with wrong name and now need to remove them without destroying volume.

2019-02-27 Thread Tami Greene
Yes, I broke it. Now I need help fixing it. I have an existing Gluster Volume, spread over 16 bricks and 4 servers; 1.5P space with 49% currently used . Added an additional 4 bricks and server as we expect large influx of data in the next 4 to 6 months. The system had been established by my

Re: [Gluster-users] Version uplift query

2019-02-27 Thread Ingo Fischer
Hi Amar, sorry to jump into this thread with an connected question. When installing via "apt-get" and so using debian packages and also systemd to start/stop glusterd is the online upgrade process from 3.x/4.x to 5.x still needed as described at

Re: [Gluster-users] Version uplift query

2019-02-27 Thread Amar Tumballi Suryanarayan
GlusterD2 is not yet called out for standalone deployments. You can happily update to glusterfs-5.x (recommend you to wait for glusterfs-5.4 which is already tagged, and waiting for packages to be built). Regards, Amar On Wed, Feb 27, 2019 at 4:46 PM ABHISHEK PALIWAL wrote: > Hi, > > Could

Re: [Gluster-users] Version uplift query

2019-02-27 Thread ABHISHEK PALIWAL
Hi, Could you please update on this and also let us know what is GlusterD2 (as it is under development in 5.0 release), so it is ok to uplift to 5.0? Regards, Abhishek On Tue, Feb 26, 2019 at 5:47 PM ABHISHEK PALIWAL wrote: > Hi, > > Currently we are using Glusterfs 3.7.6 and thinking to

Re: [Gluster-users] Gluster and bonding

2019-02-27 Thread Jorick Astrego
On 2/25/19 6:01 PM, Alvin Starr wrote: > On 2/25/19 11:48 AM, Boris Zhmurov wrote: >> On 25/02/2019 14:24, Jorick Astrego wrote: >>> >>> Hi, >>> >>> Have not measured it as we have been running this way for years now >>> and haven't experienced any problems with "transport endpoint is not >>>