Hi Adrian, I think you have two issues (and I'm sure someone can correct me if I'm mistaken) 1) At least when you use the volgen utility (in the 3.x Gluster versions) to create the config files and define RAID=1, it insists on pairs of bricks to implement this. While there is nothing that precludes multiple mirrors for RAID 1, I'm not sure Gluster accommodates that config. I may be completely wrong about this, but that has been my experience so far. 2) If Gluster does support multiple RAID 1 mirrors, you would need to do a 'ls -LR' on the top level directory of the glusterfs mount point to let Gluster see all the files and replicate accordingly. I think. I've only answered this in the hope that it may help you get started looking at the problem before most of the other mailing list users get in for work - I'm on an early shift here. James Burnash -----Original Message----- From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of Adrian Moisey Sent: Thursday, June 03, 2010 7:44 AM To: gluster-users at gluster.org Subject: Adding brick to existing glusterfs setup Hi I've got a rather simple glusterfs setup. I've got 2 servers which export a brick each, and those 2 servers mount those bricks with cluster/replicate in order to RAID1 them. I am using gluster 2.0.6. Server config: ---->8---->8---->8---->8---->8---->8---->8---->8---- volume posix type storage/posix option directory /export/ end-volume volume locks type features/locks subvolumes posix end-volume volume cache type performance/io-cache subvolumes locks end-volume volume brick type performance/io-threads option thread-count 8 subvolumes cache end-volume ### Add network serving capability to above brick. volume server type protocol/server option transport-type tcp subvolumes brick option auth.addr.brick.allow * # Allow access to "brick" volume end-volume ---->8---->8---->8---->8---->8---->8---->8---->8---- Client config: ---->8---->8---->8---->8---->8---->8---->8---->8---- ### Add client feature and attach to remote subvolume of server1 volume brick1 type protocol/client option transport-type tcp option remote-host 172.19.45.102 # IP address of the remote brick option remote-subvolume brick # name of the remote volume end-volume ### Add client feature and attach to remote subvolume of server2 volume brick2 type protocol/client option transport-type tcp option transport-timeout 5 option remote-host 172.19.45.103 # IP address of the remote brick option remote-subvolume brick # name of the remote volume end-volume volume replicate type cluster/replicate subvolumes brick1 brick2 end-volume ---->8---->8---->8---->8---->8---->8---->8---->8---- My problem is that I would like to add a third server with a third brick in order to RAID1 across all 3 servers. How do I go about doing this? I've managed to add it, but the old files aren't being replicated to the new one. -- Adrian Moisey Systems Designer | CareerJunction | Better jobs. More often. Web: www.careerjunction.co.za | Email: adrian at careerjunction.co.za Phone: +27 21 818 8621 | Mobile: +27 82 858 7830 | Fax: +27 21 818 8855 _______________________________________________ Gluster-users mailing list Gluster-users at gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users DISCLAIMER: This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this in error, please immediately notify me and permanently delete the original and any copy of any e-mail and any printout thereof. E-mail transmission cannot be guaranteed to be secure or error-free. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. NOTICE REGARDING PRIVACY AND CONFIDENTIALITY Knight Capital Group may, at its discretion, monitor and review the content of all e-mail communications. http://www.knight.com
