<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>There has been a deadlock problem in the past where both the knfs
module and the fuse module each need more memory to satisfy a fop
and neither can acquire that memory due to competing locks. This
caused an infinite wait. Not sure if anything was ever done in the
kernel to remedy that.<br>
</p>
<br>
<div class="moz-cite-prefix">On 03/07/18 11:50, Ben Mason wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAHtO4AKwxdnfQfbbdP6-j6qhZofWkiMxWfa=Nrba7vWkSrFaBw@mail.gmail.com">
<div dir="ltr">Hello,
<div><br>
</div>
<div>I'm designing a 2-node, HA NAS that must support NFS. I had
planned on using GlusterFS native NFS until I saw that it is
being deprecated. Then, I was going to use GlusterFS +
NFS-Ganesha until I saw that the Ganesha HA support ended
after 3.10 and its replacement is still a WIP. So, I landed on
GlusterFS + kernel NFS + corosync & pacemaker, which seems
to work quite well. Are there any performance issues or other
concerns with using GlusterFS as a replication layer and
kernel NFS on top of that?</div>
<div><br>
</div>
<div>Thanks!</div>
</div>
<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://lists.gluster.org/mailman/listinfo/gluster-users">http://lists.gluster.org/mailman/listinfo/gluster-users</a></pre>
</blockquote>
<br>
</body>
</html>