yes.<br><br><div class="gmail_quote">On Wed, Dec 3, 2008 at 6:08 PM, a s p a s i a <span dir="ltr"><<a href="mailto:aspasia.sf@gmail.com">aspasia.sf@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
thanks for the response!!!<br>
<div class="Ih2E3d"><br>
<br>
><br>
> Its not clear what do you mean by "dedicated server". All it needs is to<br>
> have the filesystem which has enough space to hold namespace cache (which is<br>
> small compared to actual data) and which can support large number of inodes<br>
> (the whole directory structure of unify is replicated on this node with 0<br>
> byte sized files).<br>
><br>
<br>
</div>ok, so namespace cache can be defined in the same server as any<br>
storage node brick ...such as:<br>
<br>
storage brick1 ----------- storage brick 2 ------------ storage brick<br>
3 ---------- storage brick4<br>
glusterfsd vol glustervsd vol<br>
glusterfsd vol glusterfsd vol<br>
namespace cache<br>
<br>
pls confirm.<br>
<br>
thanks again!<br>
<br>
- a.<br>
<div><div></div><div class="Wj3C7c"><br>
<br>
>><br>
>><br>
>><br>
>> • LINE 5: "option namespace namespace-child"<br>
>> The option specifies that namespace-child should be used as a place<br>
>> where the whole filesystem's namespace (ie, directory/file tree<br>
>> structure) is maintained. Here 'namespace-child' needs to be another<br>
>> volume which is already defined in the spec.<br>
>> 'namespace-child' is configured like another server brick, except that<br>
>> it's content is used to manage namespace. It should not be listed<br>
>> along with the other subvolumes.<br>
>> • LINE 6: "subvolumes child1 child2 child3 child4"<br>
>> Here 'subvolumes' is an identifier for parser to tell that following<br>
>> volumes are the 'children' nodes for current volume. 'subvolumes'<br>
>> takes one or more volume names as argument. Here child1, child2,<br>
>> child3, child4 are also named as storage nodes as these are the nodes<br>
>> where actual data is storaged.<br>
>><br>
>> ======<br>
>><br>
>> Could someone point me to a site that potentially diagrams a summary<br>
>> of a simple Gluster with Unify and AFR installed?<br>
>><br>
>> I found this site:<br>
>> <a href="http://ftp.zresearch.com/pub/gluster/glusterfs/talks/Z/GlusterFS.pdf" target="_blank">http://ftp.zresearch.com/pub/gluster/glusterfs/talks/Z/GlusterFS.pdf</a> -<br>
>> page 5 - shows the Unify stack in the client, but I still am unable to<br>
>> conceive where the metadata - single namespace information - is<br>
>> stored?<br>
>><br>
>> I apologize if my question is quite naive, but I'm a bit confused.<br>
>><br>
>> thanks in advanced,<br>
>><br>
>> aspasia.<br>
>><br>
>> _______________________________________________<br>
>> Gluster-users mailing list<br>
>> <a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
>> <a href="http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users" target="_blank">http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users</a><br>
><br>
><br>
> regards,<br>
> --<br>
> Raghavendra G<br>
><br>
><br>
<br>
<br>
<br>
</div></div><font color="#888888">--<br>
A S P A S I A<br>
. . . . . . . . . . ..<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Raghavendra G<br><br>