[Gluster-users] building bricks in AWS off an EBS snapshot

[Mayzel, Eugene]

Vijay, thanks a lot, it worked!
Still one question - why gluster did not scan its bricks for files and add that content automatically, given that the same gluster volume name already existed in the brick path?

Eugene  

-----Original Message-----
From: Mayzel, Eugene 
Sent: Friday, October 23, 2015 2:30 PM
To: 'Vijay Bellur'; gluster-users at gluster.org
Subject: RE: [Gluster-users] building bricks in AWS off an EBS snapshot

Trying now, will ping you soon, thanks!

-----Original Message-----
From: Vijay Bellur [mailto:vbellur at redhat.com]
Sent: Friday, October 23, 2015 2:27 PM
To: Mayzel, Eugene; gluster-users at gluster.org
Subject: Re: [Gluster-users] building bricks in AWS off an EBS snapshot

On Friday 23 October 2015 11:40 PM, Mayzel, Eugene wrote:
> Yes,  this is what I do, since otherwise I get the famous "already part of a volume " error.
> After extensive googling I found that the following needs to be done to clean up any past gluster traces from a brick:
>
> setfattr -x trusted.glusterfs.volume-id <brick-path> setfattr -x 
> trusted.gfid <brick-path>

Only these two steps should be sufficient. Can you try it over and check if the results are any different?

Regards,
Vijay


-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2015.0.6172 / Virus Database: 4450/10875 - Release Date: 10/23/15


The information contained in this communication is intended for the use
of the designated recipients named above. If the reader of this 
communication is not the intended recipient, you are hereby notified
that you have received this communication in error, and that any review,
dissemination, distribution or copying of this communication is strictly
prohibited. If you have received this communication in error, please 
notify The Associated Press immediately by telephone at +1-212-621-1898 
and delete this email. Thank you.
[IP_US_DISC]

msk dccc60c6d2c3a6438f0cf467d9a4938