From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 113189 invoked by alias); 10 May 2016 13:01:03 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 113160 invoked by uid 89); 10 May 2016 13:01:02 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=H*i:CADMefsZfsH, H*f:CADMefsZfsH, H*f:sk:Ci3v04n, H*i:sk:Ci3v04n X-HELO: mail-wm0-f46.google.com Received: from mail-wm0-f46.google.com (HELO mail-wm0-f46.google.com) (74.125.82.46) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Tue, 10 May 2016 13:00:52 +0000 Received: by mail-wm0-f46.google.com with SMTP id a17so26487230wme.0 for ; Tue, 10 May 2016 06:00:51 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=h+n1Ywxy+uD30D7McK7dpvAAM1K8DSWqZ1Cfdg1Ieb4=; b=YhUWvLQAlbhRBnTmkNIe2Qvgux/P3y1Aqr4mwrQ75CVrQ9DwmrMsMjSvZXNgMjMJcj NkO8ZBe/aLZ2VqyDzlbcrS+I+s2sFn7kGcUhOc173s5V1ehd+9uQTG5wJ+jwm85tHjtw SjMZqyq3WjOdNYtM84/9yJinMqRBArTAfQSGvlDwIzMcYpIowiiEY7GFwCqVzeATYrXc E5OOoVCNU/MAATxD5ZA+gFTRkMrXKf+V05XR9BAkkbP0VYUEJu3MuoXN756HN1f2VlaZ gLAMZrhbSLLG0ZxMC8gA6D56M/rvE7pE5ncNflbm/ZKDRH27MBEGs4ukxV4eYAWPoxCQ G8FQ== X-Gm-Message-State: AOPr4FVXNp7VQ/BZclufL/JSp6+qEKJz0IHa0G3/zgnoa7jdedbJ8JwDCylP0jqyxu3FSA== X-Received: by 10.28.113.218 with SMTP id d87mr18004443wmi.52.1462885249060; Tue, 10 May 2016 06:00:49 -0700 (PDT) Received: from dinwoodie.org ([2001:ba8:0:1c0::9:1]) by smtp.gmail.com with ESMTPSA id k62sm16789356wmb.7.2016.05.10.06.00.47 for (version=TLS1_2 cipher=AES128-SHA bits=128/128); Tue, 10 May 2016 06:00:48 -0700 (PDT) Date: Tue, 10 May 2016 13:01:00 -0000 From: Adam Dinwoodie To: cygwin@cygwin.com Subject: Re: Possible issue with newest version of git (v 2.8) under Cygwin Message-ID: <20160510130044.GA2345@dinwoodie.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes X-SW-Source: 2016-05/txt/msg00105.txt.bz2 On Mon, May 09, 2016 at 03:59:39PM -0400, andrew stern wrote: > If I change my fstab back so that it does not include the noacl option > on the line the merge is much faster: > > 15:51:22.288607 git.c:350 trace: built-in: git 'merge' > 'FETCH_HEAD' Updating 154cf50..a0f35eb > Fast-forward > 15:55:18.347594 run-command.c:336 trace: run_command: 'gc' '--auto' > > So it is clear that my fix for the Windows permissions is causing the > merge to take a very long time. > > > On 9 May 2016 at 14:34, andrew stern <> wrote: > > Recently I upgraded to version 2.8.0 of git on cygwin. I’m running > > under Windows 2008 R2. Before this upgrade we were able to share a > > NFS drive as a main repository. After the upgrade the permissions > > were changed so that only a single person had write access to the > > repository on a shared NFS drive. When the push is done to the NFS > > drive these permissions cause deny write access to the other users of > > the repository so we couldn’t update the sha1 of the head reference. > > An example of the incorrect permissions are: > > > > > > Allow User Special not > > inherited This folder only > > Allow dev Special not > > inherited This folder only > > Allow Everyone Read & execute not > > inherited This folder, subfolders and > > Allow Administators for machine Special not > > inherited This folder only > > Allow SYSTEM Special not > > inherited This folder only > > Allow Users for machine Special not > > inherited This folder only > > Allow CREATOR OWNER Special not > > inherited Subfolders and files only > > Allow CREATOR GROUP Special not > > inherited Subfolders and files only > > > > But the Windows permissions should have been inherited only. Also not > > the group dev is not in the list. The permissions after a push showed > > dev on the shared NFS drive along with errors that the permissions > > were out of order. > > > > Allow Administators Full Control D:\ This folder, > > subfolders and > > Allow SYSTEM Full Control D:\ This folder, > > subfolders and > > Allow User Special D:\ This folder only > > Allow CREATOR OWNER Special D:\ Subfolders > > and files only > > Allow User on Machine Read & execute D:\ This folder, > > subfolders and > > Allow User on Machine Special D:\ This folder, > > subfolders > > > > > > After searching through new groups and the web it was decided to add > > noacl to the fstab for the cygwin mount: > > > > none /cygdrive cygdrive binary,posix=0,user,noacl 0 0 > > > > Now we are finding that the git merge onto our local drive after a > > fetch from the NFS shared repository is taking a very long time. > > (shown with >> in front on below line) > > > > $ git pull origin MCSTRATEGY_4_4 > > 13:01:16.587064 git.c:351 trace: built-in: git 'pull' > > 'origin' 'MCSTRATEGY_4_4' > > 13:01:16.752064 run-command.c:336 trace: run_command: 'fetch' > > '--update-head-ok' 'origin' 'MCSTRATEGY_4_4' > > 13:01:16.790064 exec_cmd.c:120 trace: exec: 'git' 'fetch' > > '--update-head-ok' 'origin' 'MCSTRATEGY_4_4' > > 13:01:16.821064 git.c:351 trace: built-in: git 'fetch' > > '--update-head-ok' 'origin' 'MCSTRATEGY_4_4' > > 13:01:17.069064 run-command.c:336 trace: run_command: > > 'git-upload-pack > > '\''/cygdrive/s/StrategyServers/git/gitbmssorsrc.git/.'\''' > > 13:01:17.136064 run-command.c:195 trace: exec: '/bin/sh' '-c' > > 'git-upload-pack > > '\''/cygdrive/s/StrategyServers/git/gitbmssorsrc.git/.'\''' > > 'git-upload-pack > > '\''/cygdrive/s/StrategyServers/git/gitbmssorsrc.git/.'\''' > > 13:01:18.084064 run-command.c:336 trace: run_command: 'rev-list' > > '--objects' '--stdin' '--not' '--all' '--quiet' > > 13:01:18.229064 run-command.c:336 trace: run_command: 'rev-list' > > '--objects' '--stdin' '--not' '--all' > > 13:01:18.284064 exec_cmd.c:120 trace: exec: 'git' 'rev-list' > > '--objects' '--stdin' '--not' '--all' > > 13:01:18.314064 git.c:351 trace: built-in: git > > 'rev-list' '--objects' '--stdin' '--not' '--all' > > From /cygdrive/s/StrategyServers/git/gitbmssorsrc.git/. > > * branch MCSTRATEGY_4_4 -> FETCH_HEAD > > 13:01:18.367064 run-command.c:952 run_processes_parallel: > > preparing to run up to 1 tasks > > 13:01:18.373064 run-command.c:984 run_processes_parallel: done > > 13:01:18.375064 run-command.c:336 trace: run_command: 'gc' '--auto' > > 13:01:18.410064 exec_cmd.c:120 trace: exec: 'git' 'gc' '--auto' > > 13:01:18.440064 git.c:351 trace: built-in: git 'gc' '--auto' > > 13:01:18.454064 run-command.c:336 trace: run_command: 'merge' 'FETCH_HEAD' > > 13:01:18.486064 exec_cmd.c:120 trace: exec: 'git' 'merge' 'FETCH_HEAD' > >>> 13:01:18.517064 git.c:351 trace: built-in: git 'merge' 'FETCH_HEAD' > > Updating 9c40e07..a0f35eb > > Fast-forward > > 13:18:39.432839 run-command.c:336 trace: run_command: 'gc' '--auto' > > 13:18:43.559539 exec_cmd.c:120 trace: exec: 'git' 'gc' '--auto' > > 13:18:43.623539 git.c:351 trace: built-in: git 'gc' '--auto' > > file.cpp | 5 +++-- > > > > First question is could this very large delay on git merge be caused > > by the noacl? If noacl is causing this very large delay (which I > > suspect to be the case since we didn’t have this large delay till the > > noacl was added) is there another way to fix the permission issue when > > using an NFS drive as a shared repository? I suspect this isn't a problem with the Git upgrade but with recent changes that have been being made to how the core Cygwin dll handles permissions. That being said, can you try running `git config core.filemode false` in the repository, re-enabling noacl, and see if that has things running at something more like normal speed? That disables Git's checks on file permissions, so it should isolate whether the slow-down is specifically Git checking permissions or if merely accessing files is the problem. (With core.filemode disabled, you'll need to use `git update-index` to add/remove the executable flag on files in the Git repository; see `git help update-index` for details on how that works. To undo the config change, use `git config core.filemode true`.) Adam -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple