It's because currently expansion will involve either: a) increasing the capacity of existing bricks and bringing them back online to replicate changes (not super useful) b) unmounting the client file system. to add storage bricks (useful but disruptive) Growing the storage by adding a server brick without an outage is on the road map but not yet implemented. If anyone knows any different please let me know. Thanks! -Mic Burnash, James wrote: > Hello, > > I've searched through all my gluster-users archives, and I have yet to find a documented step by step procedure for adding bricks to Gluster storage in a replicated then distributed configuration. > > I did find this one post from Liam Slusser [lslusser at gmail.com] on Mon 1/4/2010 7:29 PM titled: adding another brick howto - but there were zero responses to his post. > > Since one of the stated benefits of Gluster is easy expansion, I'm frustrated by the idea that I'm going to have to hack my way through configuration files or just wholly reconfigure my PFS in order to accommodate this expansion. > > Thanks in advance for any pointers. > > James > > > > 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 > -----Original Message----- > From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of Mickey Mazarick > Sent: Monday, May 03, 2010 2:43 PM > To: Lakshmipathi > Cc: Gluster Users > Subject: Re: server ver 3.0.4 crashes > > It turns out I had a previous client version (2.09) running on a > separate server. Is there still a bug listed for this? It makes > upgrading very painful. > > Also I'm pretty sure mmaps didn't seem to work even with the > disable-direct-io option. I was running kernel ver 2.6.24.4 but ver 2.09 > works where 3.04 hangs the client (running VMs from gluster). Only some > hypervisors failed but it looked like it was a mmap problem. > > Any ideas on what would cause this? > > -Mic > Lakshmipathi wrote: > >> Hi Mickey, >> Can you please sent us the glusterfs core file and log files? >> >> >> Cheers, >> Lakshmipathi.G >> >> ----- Original Message ----- >> From: "Tejas N. Bhise" <tejas at gluster.com> >> To: "Mickey Mazarick" <mic at digitaltadpole.com> >> Cc: "Gluster Users" <gluster-users at gluster.org> >> Sent: Wednesday, April 28, 2010 9:46:07 PM >> Subject: Re: server ver 3.0.4 crashes >> >> Hi Mickey, >> >> Please open a defect in bugzilla. Someone from the dev team will have a look at it soon. >> >> Regards, >> Tejas. >> ----- Original Message ----- >> From: "Mickey Mazarick" <mic at digitaltadpole.com> >> To: "Gluster Users" <gluster-users at gluster.org> >> Sent: Wednesday, April 28, 2010 8:14:53 PM >> Subject: server ver 3.0.4 crashes >> >> Did a strait install and the ibverbs instance will crash after a >> single connection attempt. Are there any bugs that would cause this >> behavior? >> >> All the log tells me is: >> >> pending frames: >> frame : type(2) op(SETVOLUME) >> >> patchset: v3.0.4 >> signal received: 11 >> time of crash: 2010-04-28 10:41:08 >> configuration details: >> argp 1 >> backtrace 1 >> dlfcn 1 >> fdatasync 1 >> libpthread 1 >> llistxattr 1 >> setfsid 1 >> spinlock 1 >> epoll.h 1 >> xattr.h 1 >> st_atim.tv_nsec 1 >> package-string: glusterfs 3.0.4 >> /lib64/tls/libc.so.6[0x33c0a2e2b0] >> /usr/local/lib/libglusterfs.so.0(dict_unserialize+0x111)[0x2b662221d281] >> /usr/local/lib/glusterfs/3.0.4/xlator/protocol/server.so(mop_setvolume+0xa2)[0x2b6622f246e2] >> /usr/local/lib/glusterfs/3.0.4/xlator/protocol/server.so(protocol_server_interpret+0x1aa)[0x2b6622f25a0a] >> /usr/local/lib/glusterfs/3.0.4/xlator/protocol/server.so(protocol_server_pollin+0x8b)[0x2b6622f268cb] >> /usr/local/lib/glusterfs/3.0.4/xlator/protocol/server.so(notify+0x100)[0x2b6622f26aa0] >> /usr/local/lib/libglusterfs.so.0(xlator_notify+0x94)[0x2b6622221b24] >> /usr/local/lib/glusterfs/3.0.4/transport/ib-verbs.so[0x2aaaaaaaf048] >> /lib64/tls/libpthread.so.0[0x33c1906137] >> /lib64/tls/libc.so.6(__clone+0x73)[0x33c0ac7113] >> --------- >> >> >> > > > -- > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users > --
