<span id="mailbox-conversation">Great! :-)</span><div class="mailbox_signature">—<br>Rolf</div>
<br><br><div class="gmail_quote"><p>On Mon, Jun 23, 2014 at 11:55 AM, Justin Clift <span dir="ltr"><<a href="mailto:justin@gluster.org" target="_blank">justin@gluster.org</a>></span> wrote:<br></p><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><p>On 23/06/2014, at 10:50 AM, Vijay Bellur wrote:
<br>> On 06/23/2014 03:14 PM, Justin Clift wrote:
<br>>> On 23/06/2014, at 10:27 AM, Rolf Bjaanes wrote:
<br>>>> Hi Justin,
<br>>>>
<br>>>> Can we have a look at the changes to be pushed?
<br>>>
<br>>> Sure. We're just wanting the repo there to be sync'd with our canonical
<br>>> upstream one:
<br>>>
<br>>> https://git.gluster.org/glusterfs.git
<br>>>
<br>>>
<br>>>> And can someone else try to push just to eliminate some potential sources of error.
<br>>>
<br>>>
<br>>> Weirdly, I'm not a member of that project and can't add new
<br>>> members to it. (I'm a site admin?)
<br>>>
<br>>> Vijay, do you have time to add me to the project, so I can
<br>>> try pushing to it as well?
<br>>>
<br>>> https://forge.gluster.org/+glusterfscore/memberships
<br>>
<br>> You have been added as an admin to glusterfscore.
<br><br><br>Thanks Vijay. :)
<br><br>Good news too, pushing worked:
<br><br>*************************************************************
<br><br>$ git push forge master
<br>Counting objects: 2547, done.
<br>Delta compression using up to 8 threads.
<br>Compressing objects: 100% (1626/1626), done.
<br>Writing objects: 100% (2161/2161), 557.06 KiB, done.
<br>Total 2161 (delta 1495), reused 987 (delta 527)
<br>remote: => Syncing Gitorious... [OK]
<br>To git@forge.gluster.org:glusterfs-core/glusterfs.git
<br> a05c579..1e4a046 master -> master
<br><br>$ git log forge/master
<br>commit 1e4a046828ea11cb4c7738a2a00fb715f84dc1ff
<br>Author: Ravishankar N <root@ravi3.(none)>
<br>Date: Thu Jun 19 17:41:25 2014 +0000
<br><br> cluster/stripe: don't treat ESTALE as failure in lookup
<br><br> Problem:
<br> In a stripe volume, symlinks are created only on the first brick via the
<br> default_symlink() call. During gfid lookup, server sends ESTALE from the other
<br> bricks, which is treated as error in stripe_lookup_cbk()
<br><br> Fix:
<br> Don't treat ESTALE as error in stripe_lookup_cbk()
<br><br> Change-Id: Ie4ac8f0dfd3e61260161620bdc53665882e7adbd
<br> BUG: 1111454
<br> Signed-off-by: Ravishankar N <root@ravi3.(none)>
<br> Reviewed-on: http://review.gluster.org/8135
<br> Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
<br> Tested-by: Gluster Build System <jenkins@build.gluster.com>
<br> Reviewed-by: Vijay Bellur <vbellur@redhat.com>
<br><br>*************************************************************
<br><br>Rolf, I think we're ok. :)
<br><br>Regards and best wishes,
<br><br>Justin Clift
<br><br>--
<br>GlusterFS - http://www.gluster.org
<br><br>An open source, distributed file system scaling to several
<br>petabytes, and handling thousands of clients.
<br><br>My personal twitter: twitter.com/realjustinclift
<br><br></p></blockquote></div><br>