<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 10/15/2013 06:38 PM, Hafeez Bana
wrote:<br>
</div>
<blockquote
cite="mid:CAGNLXrntLWSChSGgoFhtd4ao9v6GxPZyqFyDpM5ienazFuNi2Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>Thanks Ravi, that solves it.<br>
<br>
</div>
Would it have helped if I had specified AAAHOST:nufa-r4 i.e.
removed the slash?<br>
<br>
</div>
</div>
</blockquote>
Actually it wouldn't. Nufa really applies to bricks.What enabling
nufa does is if you happen to mount the gluster volume on one of the
machines that contained a brick of that volume, then all writes from
that mount point will go that brick, irrespective of which brick the
file name hashes to.<br>
<br>
Considering a distributed volume of 3 bricks on 3 machines,<br>
Brick1: A_HOST:/brick<br>
Brick2: B_HOST:/brick<br>
Brick3: C_HOST:/brick<br>
<br>
Without nufa, the files that you create from the mount point will
hash to (i.e reside in) one of the 3 bricks depending on the
filename. <br>
With nufa enabled, if you happen to mount the voume on B_HOST, then
all files created from that mount point will always go to
B_HOST:/brick irrespective of which brick the filename really hashes
to.<br>
<blockquote
cite="mid:CAGNLXrntLWSChSGgoFhtd4ao9v6GxPZyqFyDpM5ienazFuNi2Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Asking because the documentation for nufa uses the words
sub-volumes - and as far as I understand a subvolume is a
translator with a brick underneath.<br>
</div>
</div>
</blockquote>
Well a subvolume is a brick after being processed by a translator
(<a class="moz-txt-link-freetext" href="http://www.gluster.org/community/documentation/index.php/GlusterFS_Concepts">http://www.gluster.org/community/documentation/index.php/GlusterFS_Concepts</a>).<br>
<br>
<br>
<blockquote
cite="mid:CAGNLXrntLWSChSGgoFhtd4ao9v6GxPZyqFyDpM5ienazFuNi2Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<br>
</div>
Thx again.<br>
<div>hb<br>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Tue, Oct 15, 2013 at 1:34 PM,
Ravishankar N <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:ravishankar@redhat.com" target="_blank">ravishankar@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div class="im">
<div>On 10/15/2013 02:37 PM, Hafeez Bana wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>Hi All,<br>
<br>
</div>
I've been playing with Gluster 3.4x - in
particular the nufa configuration. All the
setups are via the gluster CLI.<br>
<br>
</div>
A simple nufa config across 2 machines with
the subvolumes being bricks works without
issue. <br>
<br>
</div>
However anything more complex gives very
strange behaviors. For instance the below
config.<br>
<br>
</div>
This volume is meant to have a replica set on
each machine and then tied together into a nufa
config.<br>
<br>
</div>
I then mount nufa4 on BBBHOST and AAAHOST and
simulate some writes. This works and the speeds
seem to indicate the writes are happening locally.<br>
<br>
</div>
However the strange thing is if you look into any of
the brick dirs i.e. /DIR_ON_HOST/test004a/ - no
files are present!<br>
<div>
<div>
<div>
<div>
<div><br>
</div>
<div>The volume continues to operate but I
am baffled about<br>
</div>
<div>1) Where the files are being stored<br>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
Hi hb,<br>
The brick path present in the volume info for 'nufa4'
tells you where the files go. So<br>
<br>
Volume Name: nufa4<br>
.<br>
.
<div class="im"><br>
.<br>
Brick1: AAAHOST:/nufa-r4 <br>
Brick2: BBBHOST:/nufa-r4b<br>
<br>
</div>
means the files are created in the root file system, in
the /nufa-r4 and /nufa-r4b directories of your hosts. I
think you have misunderstood 'AAAHOST:/nufa-r4' and
'BBBHOST:/nufa-r4b' as referring to the 2 replica volumes
that you have created. They are actually the brick paths.
<div class="im"><br>
<br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>2) Whether such a configuration is
possible i.e a nufa sitting on top of 2
replica systems (and in fact how nufa
figures out which replica sit is on the
local host).<br>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</div>
Nufa makes sense only on distributed volumes. Enabling
nufa on a plain replicate volume has no effect- the files
will be created on all bricks that constitute the replica.<br>
Thanks,<br>
Ravi<br>
<blockquote type="cite">
<div>
<div class="h5">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>Any insight would be helpful.<br>
<br>
Thx.<br>
hb<br>
<br>
<br>
----------------<br>
Volume Name: nufa-r4<br>
Type: Replicate<br>
Volume ID:
d47ceecf-11be-49a3-8b27-9d1df61f588c<br>
Status: Started<br>
Number of Bricks: 1 x 2 = 2<br>
Transport-type: tcp<br>
Bricks:<br>
Brick1: AAAHOST:/DIR_ON_HOST_A/test004a<br>
Brick2: AAAHOST:/DIR_ON_HOST_A/test004b<br>
<br>
Volume Name: nufa-r4b<br>
Type: Replicate<br>
Volume ID:
98bc1402-fbd9-4637-81c2-2f24029d51bc<br>
Status: Started<br>
Number of Bricks: 1 x 2 = 2<br>
Transport-type: tcp<br>
Bricks:<br>
Brick1: BBBHOST:/DIR_ON_HOST_B/test004a<br>
Brick2: BBBHOST:/DIR_ON_HOST_B/test004b<br>
<br>
Volume Name: nufa4<br>
Type: Distribute<br>
Volume ID:
061a3359-ec92-4ab3-9305-bae783df0ec2<br>
Status: Started<br>
Number of Bricks: 2<br>
Transport-type: tcp<br>
Bricks:<br>
Brick1: AAAHOST:/nufa-r4<br>
Brick2: BBBHOST:/nufa-r4b<br>
Options Reconfigured:<br>
cluster.nufa: on<br>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div>
</div>
<pre>_______________________________________________
Gluster-users mailing list
<a moz-do-not-send="true" href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a>
<a moz-do-not-send="true" href="http://supercolony.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a></pre>
</blockquote>
<br>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>