Hi, Just tried that with the additional step (after removing the .glusterfs dir) of clearing the extended attributes of the existing files. Then issued the add-brick command but while the data are in the bricks, they have no extended attributes "attached" to them, thus they are unavailable to the gluster clients. I suppose that somehow I should instruct gluster to run through the brick folder and files and add appropriate ext attrs. a. On 13/02/2013 05:14 ??, Brian Cipriano wrote: > Hi - > > I was just looking at this yesterday. I've done some basic testing and > this seems to be possible. > > I think you're saying, you'd like to add a brick that was already > previously part of a gluster? Without losing the data that was on it, > and importing that data into the new gluster? > > All you should have to do is remove the .glusterfs folder on that > brick. Doc on that here: > > http://joejulian.name/blog/glusterfs-path-or-a-prefix-of-it-is-already-part-of-a-volume/ > > > Then running add-brick as normal. It will take a few minutes depending > on how much data is on the brick, but gluster should see that data and > rebuild its metadata accordingly. > > Again, I've only done BASIC testing, don't take my word for it. > > - brian > > On 2/13/13 7:22 AM, Alexandros Soumplis wrote: >> Hello, >> >> Is it possible to "import" data already existent in a gluster brick? >> >> a. >> >> _______________________________________________ >> Gluster-users mailing list >> Gluster-users at gluster.org >> http://supercolony.gluster.org/mailman/listinfo/gluster-users > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://supercolony.gluster.org/mailman/listinfo/gluster-users
