<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Do you mean you want to mount a gluster volume on a virtual machine?
You can do that the same way you'd do it on a real machine. You can
probably even create a brick on a virtual machine but I don't see
much point in that. <br>
<br>
But we regularly mount our gluster volume on virtual machines. We
use debian so it's as simple as this:<br>
<br>
1. service glusterfs-server start<br>
2. mount -t glusterfs localhost:/volumename /mountpoint<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 08/25/2014 12:06 AM, Chandrahasa S
wrote:<br>
</div>
<blockquote
cite="mid:OF5CB91EF9.B1EB40E3-ON65257D3F.001BE67F-65257D3F.001C176C@tcs.com"
type="cite"><font face="sans-serif" size="2">Dear All,</font>
<br>
<br>
<font face="sans-serif" size="2">Is there any way to use Glusterfs
volume
for Vmware environment.</font>
<br>
<font face="sans-serif" size="2"><br>
<br>
Chandra.</font>
<br>
<br>
<br>
<br>
<font color="#5f5f5f" face="sans-serif" size="1">From:
</font><font face="sans-serif" size="1">Ben Turner
<a class="moz-txt-link-rfc2396E" href="mailto:bturner@redhat.com"><bturner@redhat.com></a></font>
<br>
<font color="#5f5f5f" face="sans-serif" size="1">To:
</font><font face="sans-serif" size="1">Juan José Pavlik Salles
<a class="moz-txt-link-rfc2396E" href="mailto:jjpavlik@gmail.com"><jjpavlik@gmail.com></a></font>
<br>
<font color="#5f5f5f" face="sans-serif" size="1">Cc:
</font><font face="sans-serif" size="1"><a class="moz-txt-link-abbreviated" href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a></font>
<br>
<font color="#5f5f5f" face="sans-serif" size="1">Date:
</font><font face="sans-serif" size="1">08/22/2014 08:57 PM</font>
<br>
<font color="#5f5f5f" face="sans-serif" size="1">Subject:
</font><font face="sans-serif" size="1">Re: [Gluster-users]
Gluster 3.5.2 gluster, how does cache work?</font>
<br>
<font color="#5f5f5f" face="sans-serif" size="1">Sent by:
</font><font face="sans-serif" size="1"><a class="moz-txt-link-abbreviated" href="mailto:gluster-users-bounces@gluster.org">gluster-users-bounces@gluster.org</a></font>
<br>
<hr noshade="noshade">
<br>
<br>
<br>
<tt><font size="2">----- Original Message -----<br>
> From: "Juan José Pavlik Salles"
<a class="moz-txt-link-rfc2396E" href="mailto:jjpavlik@gmail.com"><jjpavlik@gmail.com></a><br>
> To: <a class="moz-txt-link-abbreviated" href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a><br>
> Sent: Thursday, August 21, 2014 4:07:28 PM<br>
> Subject: [Gluster-users] Gluster 3.5.2 gluster, how does
cache work?<br>
> <br>
> Hi guys, I've been reading a bit about caching in gluster
volumes,
but I<br>
> still don't get a few things. I set up a gluster replica
2 volume
like this:<br>
> <br>
> [root@gluster-test-1 ~]# gluster vol info vol_rep<br>
> Volume Name: vol_rep<br>
> Type: Replicate<br>
> Volume ID: b77db06d-2686-46c7-951f-e43bde21d8ec<br>
> Status: Started<br>
> Number of Bricks: 1 x 2 = 2<br>
> Transport-type: tcp<br>
> Bricks:<br>
> Brick1: gluster-test-1:/ladrillos/l1/l<br>
> Brick2: gluster-test-2:/ladrillos/l1/l<br>
> Options Reconfigured:<br>
> performance.cache-min-file-size: 90MB<br>
> performance.cache-max-file-size: 256MB<br>
> performance.cache-refresh-timeout: 60<br>
> performance.cache-size: 256MB<br>
> [root@gluster-test-1 ~]#<br>
> <br>
> Then I mounted the volume with gluster client on another
machine.
I created<br>
> an 80Mbytes file called 80, and here you have the reading
test:<br>
> <br>
> [root@gluster-client-1 gluster_vol]# dd
if=/mnt/gluster_vol/80 of=/dev/null<br>
> bs=1M<br>
> 80+0 records in<br>
> 80+0 records out<br>
> 83886080 bytes (84 MB) copied, 1,34145 s, 62,5 MB/s<br>
> [root@gluster-client-1 gluster_vol]# dd
if=/mnt/gluster_vol/80 of=/dev/null<br>
> bs=1M<br>
> 80+0 records in<br>
> 80+0 records out<br>
> 83886080 bytes (84 MB) copied, 0,0246918 s, 3,4 GB/s<br>
> [root@gluster-client-1 gluster_vol]# dd
if=/mnt/gluster_vol/80 of=/dev/null<br>
> bs=1M<br>
> 80+0 records in<br>
> 80+0 records out<br>
> 83886080 bytes (84 MB) copied, 0,0195678 s, 4,3 GB/s<br>
> [root@gluster-client-1 gluster_vol]#<br>
<br>
You are seeing the effect of client side kernel caching. If
you want
to see the actual throughput for reads run:<br>
<br>
sync; echo 3 > /proc/sys/vm/drop_caches; dd blah<br>
<br>
Kernel caching happens on both the client and server side,
when I want
to see uncached performance I drop caches on both clients and
servers:<br>
<br>
run_drop_cache()<br>
{<br>
for host in $MASTERNODE $NODE $CLIENT<br>
do<br>
ssh -i /root/.ssh/my_id root@${host} echo "Dropping
cache on $host"<br>
ssh -i /root/.ssh/my_id root@${host} sync<br>
ssh -i /root/.ssh/my_id root@${host} "echo
3 > /proc/sys/vm/drop_caches"<br>
done<br>
}<br>
<br>
HTH!<br>
<br>
-b<br>
<br>
> Cache is working flawlessly, (even though that 80 Mbytes
is smaller
than the<br>
> min-file-size value, but I don't care about it right now)
what I don't
get<br>
> is where cache is being stored. Is it stored on the
client side or
on the<br>
> server side? According to documentation, the io-cache
translator could
be<br>
> loaded on both sides (client and server), how can I know
where it
is being<br>
> loeaded? It looks like as it was being stored locally
because of the
speed,<br>
> but I'd like to be sure.<br>
> <br>
> Thanks!<br>
> <br>
> --<br>
> Pavlik Salles Juan José<br>
> Blog - </font></tt><a moz-do-not-send="true"
href="http://viviendolared.blogspot.com/"><tt><font size="2">http://viviendolared.blogspot.com</font></tt></a><tt><font
size="2"><br>
> <br>
> _______________________________________________<br>
> Gluster-users mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
> </font></tt><a moz-do-not-send="true"
href="http://supercolony.gluster.org/mailman/listinfo/gluster-users"><tt><font
size="2">http://supercolony.gluster.org/mailman/listinfo/gluster-users</font></tt></a><tt><font
size="2"><br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
</font></tt><a moz-do-not-send="true"
href="http://supercolony.gluster.org/mailman/listinfo/gluster-users"><tt><font
size="2">http://supercolony.gluster.org/mailman/listinfo/gluster-users</font></tt></a>
<br>
<p>=====-----=====-----=====<br>
Notice: The information contained in this e-mail<br>
message and/or attachments to it may contain <br>
confidential or privileged information. If you are <br>
not the intended recipient, any dissemination, use, <br>
review, distribution, printing or copying of the <br>
information contained in this e-mail message <br>
and/or attachments to it are strictly prohibited. If <br>
you have received this communication in error, <br>
please notify us by reply e-mail or telephone and <br>
immediately and permanently delete the message <br>
and any attachments. Thank you</p>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gluster-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a>
<a class="moz-txt-link-freetext" href="http://supercolony.gluster.org/mailman/listinfo/gluster-users">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a></pre>
</blockquote>
<br>
</body>
</html>