Re: [Gluster-users] [Gluster-devel] Query!

Yes, you'd need to construct everything from scratch in this case. -Atin Sent from one plus one On 23-May-2016 8:33 AM, "ABHISHEK PALIWAL" wrote: > Hi Atin, > > Thanks for your reply. But we fall in this situation then what is the > solution to recover from here I have

Re: [Gluster-users] [Gluster-devel] Query!

Hi Atin, Thanks for your reply. But we fall in this situation then what is the solution to recover from here I have already remove /var/log/glusterd from one peer, should I need to remove /var/log/glusterd from both of the peers. Regards, Abhishek On Fri, May 20, 2016 at 8:39 PM, Atin Mukherjee

Re: [Gluster-users] [Gluster-devel] Query!

-Atin Sent from one plus one On 20-May-2016 5:34 PM, "ABHISHEK PALIWAL" wrote: > > Actually we have some other files related to system initial configuration for that we > need to format the volume where these bricks are also created and after this we are > facing some

Re: [Gluster-users] [Gluster-devel] Query!

Actually we have some other files related to system initial configuration for that we need to format the volume where these bricks are also created and after this we are facing some abnormal behavior in gluster and some failure logs like volume ID mismatch something. That is why I am asking this

Re: [Gluster-users] [Gluster-devel] Query!

And most importantly why would you do that? What's your use case Abhishek? On 05/20/2016 05:03 PM, Lindsay Mathieson wrote: > On 20/05/2016 8:37 PM, ABHISHEK PALIWAL wrote: >> I am not getting any failure and after restart the glusterd when I run >> volume info command it creates the brick

Re: [Gluster-users] [Gluster-devel] Query!

On 20/05/2016 8:37 PM, ABHISHEK PALIWAL wrote: I am not getting any failure and after restart the glusterd when I run volume info command it creates the brick directory as well as .glsuterfs (xattrs). but some time even after restart the glusterd, volume info command showing no volume

Re: [Gluster-users] [Gluster-devel] Query!

I am not getting any failure and after restart the glusterd when I run volume info command it creates the brick directory as well as .glsuterfs (xattrs). but some time even after restart the glusterd, volume info command showing no volume present. Could you please tell me why this unpredictable

Re: [Gluster-users] [Gluster-devel] Query!

This would erase the xattrs set on the brick root (volume-id), which identify it as a brick. Brick processes will fail to start when this xattr isn't present. On Fri, May 20, 2016 at 3:42 PM, ABHISHEK PALIWAL wrote: > Hi > > What will happen if we format the volume

Re: [Gluster-users] [Gluster-devel] Query on healing process

Then how can I resolved this issue? On Mon, Mar 14, 2016 at 1:37 PM, Ravishankar N wrote: > On 03/14/2016 10:36 AM, ABHISHEK PALIWAL wrote: > > Hi Ravishankar, > > I just want to inform that this file have some different properties from > other files like this is the

Re: [Gluster-users] [Gluster-devel] Query on healing process

On 03/14/2016 10:36 AM, ABHISHEK PALIWAL wrote: Hi Ravishankar, I just want to inform that this file have some different properties from other files like this is the file which having the fixed size and when there is no space in file the next data will start wrapping from the top of the

Re: [Gluster-users] [Gluster-devel] Query on healing process

Hi Ravishankar, I just want to inform that this file have some different properties from other files like this is the file which having the fixed size and when there is no space in file the next data will start wrapping from the top of the file. Means in this file we are doing the wrapping of

Re: [Gluster-users] [Gluster-devel] Query on healing process

On Fri, Mar 4, 2016 at 6:36 PM, Ravishankar N wrote: > On 03/04/2016 06:23 PM, ABHISHEK PALIWAL wrote: > > >> Ok, just to confirm, glusterd and other brick processes are running >> after this node rebooted? >> When you run the above command, you need to check >>

Re: [Gluster-users] [Gluster-devel] Query on healing process

On 03/04/2016 06:23 PM, ABHISHEK PALIWAL wrote: Ok, just to confirm, glusterd and other brick processes are running after this node rebooted? When you run the above command, you need to check /var/log/glusterfs/glfsheal-volname.log logs errros. Setting client-log-level to

Re: [Gluster-users] [Gluster-devel] Query on healing process

On Fri, Mar 4, 2016 at 5:31 PM, Ravishankar N wrote: > On 03/04/2016 12:10 PM, ABHISHEK PALIWAL wrote: > > Hi Ravi, > > 3. On the rebooted node, do you have ssl enabled by any chance? There is a > bug for "Not able to fetch volfile' when ssl is enabled: >

Re: [Gluster-users] [Gluster-devel] Query on healing process

On 03/04/2016 12:10 PM, ABHISHEK PALIWAL wrote: Hi Ravi, 3. On the rebooted node, do you have ssl enabled by any chance? There is a bug for "Not able to fetch volfile' when ssl is enabled: https://bugzilla.redhat.com/show_bug.cgi?id=1258931 -> I have checked but ssl is disabled but

Re: [Gluster-users] [Gluster-devel] Query on healing process

Hi Ravi, 3. On the rebooted node, do you have ssl enabled by any chance? There is a bug for "Not able to fetch volfile' when ssl is enabled: https://bugzilla.redhat.com/show_bug.cgi?id=1258931 -> I have checked but ssl is disabled but still getting these errors # gluster volume heal

Re: [Gluster-users] [Gluster-devel] Query on healing process

On Thu, Mar 3, 2016 at 4:10 PM, Ravishankar N wrote: > Hi, > > On 03/03/2016 11:14 AM, ABHISHEK PALIWAL wrote: > > Hi Ravi, > > As I discussed earlier this issue, I investigated this issue and find that > healing is not triggered because the "gluster volume heal