HI Eliezer, I know about those attributes. In this instance they were untouched because I'm re-using the original brick. The part I'm confused about is how to use those attributes to show there are pending operations. Regards, John On 30/06/14 13:24, Eliezer Croitoru wrote: > There are some extended acls or attributes that glustefs uses for > bricks that needs to be removed: > > I think this explains more then I can: > http://linuxsysadm.wordpress.com/2013/05/16/glusterfs-remove-extended-attributes-to-completely-remove-bricks/ > > > Eliezer > On 06/30/2014 06:18 AM, John Gardeniers wrote: >> 1) While gluster was stopped I merely did an rm -rf on both the data >> sub-directory and the .gluster sub-directory. How do I show that there >> are pending operations? >> 2) Yes, I did run that. > > _______________________________________________ > Gluster-users mailing list > Gluster-users@xxxxxxxxxxx > http://supercolony.gluster.org/mailman/listinfo/gluster-users > > ______________________________________________________________________ > This email has been scanned by the Symantec Email Security.cloud service. > For more information please visit http://www.symanteccloud.com > ______________________________________________________________________ _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
