Re: [Gluster-devel] Query!

[ABHISHEK PALIWAL <abhishpaliwal@xxxxxxxxx>]

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.

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 <amukherj@xxxxxxxxxx> 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@xxxxxxxxxxx
> http://www.gluster.org/mailman/listinfo/gluster-users
>

--

Regards
Abhishek Paliwal

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users