<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Dear All,<br><br>I've made much progress on the mounting side of things - glusterfs is now clustering perfectly my Debian sub-servers in my "head" Leopard xServe - but I was still unable to write to the mounted filesystem without errors/refusals, and I only recently understood why: my xServe is unable to read/write to an xfs filesystem that is mounted into the local userspace through macfuse.<br><br>I know that without macFuse on a Leopard server, glusterfs has "server-only" capabilities. I also read that it is possible to re-export a glusterfs cluster through nfs, which leopard is able to understand - but I read that (a non-kernel) Fuse is necessary to do this, yet if the filesystem is first mounted into the local userspace, Leopard won't be able to read it! Catch-22...<br><br>For the time being, the only solution I see is to redo my network architecture to make one of the Debian sub-servers the nfs exporter (instead of having the Debian servers clustered and mounted in the Leopard head server) - yet is it possible that a unique Debian server be both a client and server? This way I could have a Debian server cluster and NFS-export two other debian servers, at the same time as being part of another cluster mounted on another Debian server. Does this sound feasable?<br><br>Thanks, best,<br><br>Josef.<div><br><div><div>On Jan 7, 2009, at 10:32 , <a href="mailto:admin@matphot.com">admin@matphot.com</a> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Dear Amar,<div><br></div><div>Hello - did you manage to look into the directory related problems since?</div><div><br></div><div>Thank you,</div><div><br></div><div>Josef.</div><div><br><div><div>On Jan 3, 2009, at 09:53 , Amar Tumballi (bulde) wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">hi 'At Work',<br> I got similar report in another user of glusterfs in macfuse mailing list too. I will look into this mac 'directory' related issues on monday. Will get back to you after I investigate it.<br> <br>Regards,<br>Amar<br><br><div class="gmail_quote">2009/1/3 At Work <span dir="ltr"><<a href="mailto:admin@matphot.com">admin@matphot.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div style=""><blockquote type="cite"> </blockquote><div>What's more, I see that the proper permissions and UID are being forwarded to the remote filesystem - as the user of the service creating the files exists only on the "head" server, is it possible that it is the remote server is refusing to do a mkdir and chown directories? This would be odd, as it would seem logical that it would be the mount-point server that would decide who gets to read or write.</div> <div><br></div><div>What of the "glusterfs-fuse" error I get every two seconds? Is this in your domain, or should I be asking this of the FUSE developers?</div><div><br></div><div>Thanks, best.</div><br><blockquote type="cite"> <div><div></div><div class="Wj3C7c">That's it exactly. As it stands I have glusterfs server (or its server.vol file) on the sub-servers setting up (and exporting?) the bricks, and the OS X uses only the client.vol file to import and assemble the remote bricks into a cluster. Also, yes, the problems are as you say: I can read/write files, but I cannot create/upload/rename directories.<div> <br></div><div>Here is a copy of the server.vol files from two servers:</div><div><br></div><blockquote style="border: medium none ; margin: 0pt 0pt 0pt 40px; padding: 0px;"><b>matserve01</b>:</blockquote><div><br></div><blockquote style="border: medium none ; margin: 0pt 0pt 0pt 40px; padding: 0px;"> volume posix01a<br> type storage/posix <br> option directory /raid01a/clients<br>end-volume<br><br>volume raid01a<br> type features/locks<br> subvolumes posix01a<br>end-volume<br><br>volume posix01b<br> type storage/posix<br> option directory /raid01b/clients<br>end-volume<br><br>volume raid01b<br> type features/locks<br> subvolumes posix01b<br>end-volume<br><br><br>### Add network serving capability to above exports.<br>volume server<br> type protocol/server<br> option transport-type tcp<br> subvolumes raid01a raid01b<br> option auth.addr.raid01a.allow 192.168.1.* # Allow access to "raid01a" volume<br> option auth.addr.raid01b.allow 192.168.1.* # Allow access to "raid01b" volume<br> end-volume</blockquote><div><div><br></div></div><div><br></div><blockquote style="border: medium none ; margin: 0pt 0pt 0pt 40px; padding: 0px;"><b>matserve02:</b><br><br>volume posix02a<br> type storage/posix <br> option directory /raid02a/clients<br> end-volume<br><br>volume raid02a<br> type features/locks<br> subvolumes posix02a<br>end-volume<br><br>volume posix02b<br> type storage/posix<br> option directory /raid02b/clients<br>end-volume<br><br>volume raid02b<br> type features/locks<br> subvolumes posix02b<br>end-volume<br><br>### Add network serving capability to above exports.<br>volume server<br> type protocol/server<br> option transport-type tcp<br> subvolumes raid02a raid02b<br> option auth.addr.raid02a.allow 192.168.1.* # Allow access to "raid02a" volume<br> option auth.addr.raid02b.allow 192.168.1.* # Allow access to "raid02b" volume<br>end-volume</blockquote><div><div><br></div></div><div>...and the client.vol file from the OS X server.</div><div><br></div><blockquote style="border: medium none ; margin: 0pt 0pt 0pt 40px; padding: 0px;"> ### Add client feature and attach to remote subvolume of server1<br><br># import RAID a's on matserve01 & matserve02 <br><br>volume rRaid01a<br> type protocol/client<br> option transport-type tcp/client<br> option remote-host 192.168.1.6 # IP address of the remote brick<br> option remote-subvolume raid01a # name of the remote volume<br>end-volume<br><br>volume rRaid02a<br> type protocol/client<br> option transport-type tcp/client<br> option remote-host 192.168.1.7 # IP address of the remote brick<br> option remote-subvolume raid02a # name of the remote volume<br>end-volume<br><br>## add c, d, e, etc sections as bays expand for each server<br>###################<br><br>### Add client feature and attach to remote subvolume of server2<br> <br># combine raid a's<br>volume cluster0102a<br> type cluster/afr<br> subvolumes rRaid01a rRaid02a<br>end-volume<br><br>## add c, d, e, etc sections as bays expand for each server<br>###################</blockquote><div> <div><br></div></div><div><br></div><div>...you may notice that I am for the time being assembling but one cluster (a) - for testing purposes.</div><div><br></div><div>Does all this seem correct to you?</div><div><br></div> <div><br></div></div></div><div><div><div><div></div><div class="Wj3C7c"><div>On Jan 2, 2009, at 14:17 , Krishna Srinivas wrote:</div><br></div></div><div><div></div><div class="Wj3C7c"><blockquote type="cite"><div>Schomburg,<br> <br>You have 4 servers and one client. Each server has to export 2<br>directories /raid01a and /raid01b (FUSE do not play any role on the<br>servers). On the client machine the glusterfs mounts using the client<br>vol file combining all the exported directories. This would be a<br> typical setup in your case. How is your setup? Can you mail the client<br>vol file? According to your mail creation of directory fails. But<br>creation/read/write of files are fine. Right?<br><br>Krishna<br><br>On Fri, Jan 2, 2009 at 5:01 PM, Jake Maul <<a href="mailto:jakemaul@gmail.com" target="_blank">jakemaul@gmail.com</a>> wrote:<br> <blockquote type="cite">On Fri, Jan 2, 2009 at 3:55 AM, At Work <<a href="mailto:admin@matphot.com" target="_blank">admin@matphot.com</a>> wrote:<br></blockquote><blockquote type="cite"><blockquote type="cite">Thank you for your rapid reply. Just one question: by "leave your fstab<br> </blockquote></blockquote><blockquote type="cite"><blockquote type="cite">mount alone" do you mean leave it mount the xfs disk on startup?<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> Yes. Mount your XFS partition via fstab as you normally would.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">As for the rest.... dunno what to tell ya. Maybe one of the glusterfs<br></blockquote> <blockquote type="cite">devs can chime in with some ideas.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Good luck,<br></blockquote><blockquote type="cite">Jake<br></blockquote><blockquote type="cite"> <br></blockquote><blockquote type="cite"><blockquote type="cite">This problem is odd to say the least - when I do a 'mount' after activating<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> the glusterfs client and cluster on Leopard, I get the following:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> glusterfs on /Volumes/raid0102a (fusefs, local, synchronous)<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> ...and on the Debian host server I get:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> fusectl on /sys/fs/fuse/connections type fusectl (rw) # seems to be a<br> </blockquote></blockquote><blockquote type="cite"><blockquote type="cite">fuse connection - should fuse-accessible mounts go here?<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> /dev/sdb1 on /raid01a type xfs (rw) # raid block a<br> </blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> /dev/sdc1 on /raid01b type xfs (rw) # raid block b<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote> </blockquote><blockquote type="cite"><blockquote type="cite">...and in the glusterfs log I get:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"> <blockquote type="cite">2009-01-02 11:06:42 E [fuse-bridge.c:279:fuse_loc_fill] fuse-bridge: failed<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">to search parent for 576 ((null))<br></blockquote> </blockquote><blockquote type="cite"><blockquote type="cite">2009-01-02 11:06:42 E [fuse-bridge.c:703:do_chmod] glusterfs-fuse: 2: CHMOD<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">576 ((null)) (fuse_loc_fill() failed)<br> </blockquote></blockquote><blockquote type="cite"><blockquote type="cite">2009-01-02 11:06:42 E [fuse-bridge.c:279:fuse_loc_fill] fuse-bridge: failed<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> to search parent for 576 ((null))<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">2009-01-02 11:06:42 E [fuse-bridge.c:581:fuse_getattr] glusterfs-fuse: 1:<br></blockquote></blockquote><blockquote type="cite"> <blockquote type="cite">GETATTR 576 (fuse_loc_fill() failed)<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">2009-01-02 11:08:16 E [fuse-bridge.c:279:fuse_loc_fill] fuse-bridge: failed<br></blockquote> </blockquote><blockquote type="cite"><blockquote type="cite">to search parent for 578 ((null))<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">2009-01-02 11:08:16 E [fuse-bridge.c:2193:fuse_getxattr] glusterfs-fuse: 2:<br> </blockquote></blockquote><blockquote type="cite"><blockquote type="cite">GETXATTR (null)/578 (com.apple.FinderInfo) (fuse_loc_fill() failed)<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">2009-01-02 11:08:16 E [fuse-bridge.c:279:fuse_loc_fill] fuse-bridge: failed<br> </blockquote></blockquote><blockquote type="cite"><blockquote type="cite">to search parent for 578 ((null))<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">2009-01-02 11:08:16 E [fuse-bridge.c:2193:fuse_getxattr] glusterfs-fuse: 2:<br> </blockquote></blockquote><blockquote type="cite"><blockquote type="cite">GETXATTR (null)/578 (com.apple.FinderInfo) (fuse_loc_fill() failed)<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">2009-01-02 11:08:17 E [fuse-bridge.c:279:fuse_loc_fill] fuse-bridge: failed<br> </blockquote></blockquote><blockquote type="cite"><blockquote type="cite">to search parent for 578 ((null))<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">2009-01-02 11:08:17 E [fuse-bridge.c:2193:fuse_getxattr] glusterfs-fuse: 0:<br> </blockquote></blockquote><blockquote type="cite"><blockquote type="cite">GETXATTR (null)/578 (com.apple.FinderInfo) (fuse_loc_fill() failed)<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">2009-01-02 11:09:58 E [fuse-bridge.c:279:fuse_loc_fill] fuse-bridge: failed<br> </blockquote></blockquote><blockquote type="cite"><blockquote type="cite">to search parent for 578 ((null))<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">2009-01-02 11:09:58 E [fuse-bridge.c:581:fuse_getattr] glusterfs-fuse: 1:<br> </blockquote></blockquote><blockquote type="cite"><blockquote type="cite">GETATTR 578 (fuse_loc_fill() failed)<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"> <blockquote type="cite">...and the last two lines are repeated every few minutes.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> Am I correct in understanding that I have no need for FUSE on the Debian<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">servers? There seems to be a bridge-failure of some sort going on here.<br> </blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> <br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">On Jan 2, 2009, at 08:34 , Jake Maul wrote:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote> <blockquote type="cite"><blockquote type="cite"><blockquote type="cite">On the brick server (the content server... the one with the<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> <blockquote type="cite">XFS-formatted volume), FUSE is actually not used or even needed as far<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">as I can tell. Leave your fstab mount alone, and treat GlusterFS as a<br> </blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">pure replacement for NFS's /etc/exports.<br></blockquote></blockquote></blockquote><blockquote type="cite"> <blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">FUSE only comes into play on the client side, where it's no longer<br> </blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">relevant what the underlying filesystem is. If I'm reading you right,<br></blockquote></blockquote></blockquote> <blockquote type="cite"><blockquote type="cite"><blockquote type="cite">your XServe is the client in this scenario. Perhaps Mac OSX's FUSE<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> <blockquote type="cite">implementation is strange somehow, I'm not familiar with it.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Otherwise, it sounds to me like you're doing it right. Sounds like<br> </blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">either a permissions problem or a bug somewhere (first guesses would<br></blockquote></blockquote></blockquote> <blockquote type="cite"><blockquote type="cite"><blockquote type="cite">be Mac OSX's FUSE, or GlusterFS client on OSX).<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> <br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">On Thu, Jan 1, 2009 at 11:55 PM, <a href="mailto:admin@matphot.com" target="_blank">admin@matphot.com</a> <<a href="mailto:admin@matphot.com" target="_blank">admin@matphot.com</a>><br> </blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">wrote:<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> <blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Dear All,<br></blockquote></blockquote></blockquote> </blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> <blockquote type="cite">I'm afraid I'm a bit new to this. I hope I'm not missing the obvious, but<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> <blockquote type="cite">in<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">all the documentation I can't seem to find a clear answer to my problem.<br> </blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"> <blockquote type="cite"><blockquote type="cite"><blockquote type="cite">I have a head server (Leopard X serve) that will be used as a mount point<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"> <blockquote type="cite"><blockquote type="cite"><blockquote type="cite">for four sub-servers (Debian Etch) that each have two SATA RAID 5 blocks<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"> <blockquote type="cite"><blockquote type="cite"><blockquote type="cite">running an XFS filesystem.<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> <blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Before I switched to glusterfs, I would do an NFS export (/etc/exports)<br> </blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">of<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"> <blockquote type="cite"><blockquote type="cite"><blockquote type="cite">the XFS filesystem mounted in /etc/fstab. I have since cancelled<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> <blockquote type="cite"><blockquote type="cite">(commented<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">out) the NFS export, but I am not quite sure what to do about the fstab:<br> </blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Should I mount the drives using this file, then export the filesystem<br> </blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">using<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"> <blockquote type="cite"><blockquote type="cite"><blockquote type="cite">glusterfs? Or should it be glusterfs doing the mounting? What role does<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"> <blockquote type="cite"><blockquote type="cite"><blockquote type="cite">FUSE<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> have in the mount operation?<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote> </blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">The RAID drives are at /dev/sdb and /dev/sdc, and their filesystems are<br></blockquote></blockquote></blockquote> </blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">accessible at /dev/sdb1 and /dev/sdc1 - should I be mounting these with<br></blockquote></blockquote></blockquote> </blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">glusterfs (instead of mounting them to a folder in the server root as I<br></blockquote></blockquote></blockquote> </blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">am<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> <blockquote type="cite">doing presently)?<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote> </blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">With my present configuration, all works correctly if I mount the raid<br></blockquote></blockquote> </blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">drives individually, yet when I mirror two drives across two servers<br></blockquote></blockquote></blockquote> </blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">using<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> <blockquote type="cite">AFS things get wonky - I can upload files to a folder (and see that they<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> <blockquote type="cite">have indeed been replicated to both drives), yet I am unable to create a<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> <blockquote type="cite">new<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">folder (it becomes an inaccessible icon).<br> </blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"> <blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Thank you for any advice.<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> <blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Best,<br></blockquote></blockquote></blockquote> </blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> <blockquote type="cite">J.M. Schomburg.<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote> </blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> <blockquote type="cite"><blockquote type="cite">_______________________________________________<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> <blockquote type="cite">Gluster-devel mailing list<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><a href="mailto:Gluster-devel@nongnu.org" target="_blank">Gluster-devel@nongnu.org</a><br> </blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><a href="http://lists.nongnu.org/mailman/listinfo/gluster-devel" target="_blank">http://lists.nongnu.org/mailman/listinfo/gluster-devel</a><br> </blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"> <blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"> <blockquote type="cite"><blockquote type="cite">_______________________________________________<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Gluster-devel mailing list<br> </blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><a href="mailto:Gluster-devel@nongnu.org" target="_blank">Gluster-devel@nongnu.org</a><br></blockquote></blockquote> </blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><a href="http://lists.nongnu.org/mailman/listinfo/gluster-devel" target="_blank">http://lists.nongnu.org/mailman/listinfo/gluster-devel</a><br> </blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> <br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite"> Gluster-devel mailing list<br></blockquote><blockquote type="cite"><a href="mailto:Gluster-devel@nongnu.org" target="_blank">Gluster-devel@nongnu.org</a><br></blockquote><blockquote type="cite"><a href="http://lists.nongnu.org/mailman/listinfo/gluster-devel" target="_blank">http://lists.nongnu.org/mailman/listinfo/gluster-devel</a><br> </blockquote><blockquote type="cite"><br></blockquote></div></blockquote></div></div></div><br></div><div><div></div><div class="Wj3C7c"><div style="margin: 0px;">_______________________________________________</div><div style="margin: 0px;"> Gluster-devel mailing list</div><div style="margin: 0px;"><a href="mailto:Gluster-devel@nongnu.org" target="_blank">Gluster-devel@nongnu.org</a></div><div style="margin: 0px;"><a href="http://lists.nongnu.org/mailman/listinfo/gluster-devel" target="_blank">http://lists.nongnu.org/mailman/listinfo/gluster-devel</a></div> </div></div></blockquote> </div><br>_______________________________________________<br> Gluster-devel mailing list<br> <a href="mailto:Gluster-devel@nongnu.org">Gluster-devel@nongnu.org</a><br> <a href="http://lists.nongnu.org/mailman/listinfo/gluster-devel" target="_blank">http://lists.nongnu.org/mailman/listinfo/gluster-devel</a><br> <br></blockquote></div><br><br clear="all"><br>-- <br>Amar Tumballi<br>Gluster/GlusterFS Hacker<br>[bulde on #gluster/<a href="http://irc.gnu.org">irc.gnu.org</a>]<br><a href="http://www.zresearch.com">http://www.zresearch.com</a> - Commoditizing Super Storage!<br> </blockquote></div><br></div></div></blockquote></div><br></div></body></html>