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" <abhishpali...@gmail.com> wrote:
> 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 < > atin.mukherje...@gmail.com> wrote: > >> -Atin >> Sent from one plus one >> On 20-May-2016 5:34 PM, "ABHISHEK PALIWAL" <abhishpali...@gmail.com> >> 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 abnormal behavior in gluster and some failure logs like >> volume ID mismatch something. >> > >> > That is why I am asking this is the right way to format volume where >> bricks are created. >> >> No certainly not. If you format your brick, you loose the data and so as >> all the extended attributes. In this case your volume would bound to behave >> abnormally. >> >> > >> > and also is there any link between /var/lib/glusterd and xattr stored >> in .glusterfs directory at brick path. >> > >> > Regards, >> > Abhishek >> > >> > On Fri, May 20, 2016 at 5:25 PM, Atin Mukherjee <amukh...@redhat.com> >> wrote: >> >> >> >> 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 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 problem is >> occurring. >> >> >> >> >> > >> >> > Because as stated earlier you erase all the information about the >> >> > brick? How is this unpredictable? >> >> > >> >> > >> >> > If you want to delete and recreate a brick you should have used the >> >> > remove-brick/add-brick commands. >> >> > >> >> > -- >> >> > Lindsay Mathieson >> >> > >> >> > >> >> > >> >> > _______________________________________________ >> >> > Gluster-users mailing list >> >> > Gluster-users@gluster.org >> >> > http://www.gluster.org/mailman/listinfo/gluster-users >> >> > >> > >> > >> > >> > >> > -- >> > >> > >> > >> > >> > Regards >> > Abhishek Paliwal >> > >> > _______________________________________________ >> > Gluster-users mailing list >> > Gluster-users@gluster.org >> > http://www.gluster.org/mailman/listinfo/gluster-users >> >> -Atin >> Sent from one plus one >> > > > > -- > > > > > Regards > Abhishek Paliwal >
_______________________________________________ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users