From: "Tim Walter (Visual Concepts)" <twalter@vcentertainment.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: RE: git hangs with --separate-git-dir
Date: Tue, 16 May 2023 21:55:35 +0000 [thread overview]
Message-ID: <BY5PR14MB36541924E1E6E5E912AFE0C2A5799@BY5PR14MB3654.namprd14.prod.outlook.com> (raw)
In-Reply-To: <ZGP2AzYJSLpI4kGN@tapette.crustytoothpaste.net>
---TAW replies below---
-----Original Message-----
From: brian m. carlson <sandals@crustytoothpaste.net>
Sent: Tuesday, May 16, 2023 2:31 PM
To: Tim Walter (Visual Concepts) <twalter@vcentertainment.com>
Cc: git@vger.kernel.org
Subject: Re: git hangs with --separate-git-dir
On 2023-05-16 at 17:54:41, Tim Walter (Visual Concepts) wrote:
> Windows 10 PC
> large project
> 300GB
> 500,000 files
> mix of binary and text assets.
>
> cd /d D:\myproject
> git init --separate-git-dir=F:\myproject.git
> git add *
>
> Git runs for a little while then hangs and does some really bad things to the OS as well.
> it seems impossible to kill git.exe even with administrator priviledges.
> f: drive ends up locked and any other process, such as explorer that
> try to look at it also hang you cannot log out without hanging or even
> restart This then requires a hard power cycle to fix.
>
> 100% reproducable.
>
> running git init without --separate-git-dir and git add * works fine
> (takes 3 hours,.. but works) then I can move the .git dir to f: and reinit with --separate-git-dir and that works.
> So this seems to only be a problem for the initial init.
I don't use Windows so I can't verify this, but I would not expect this problem to occur. Even hashing 500,000 files consuming 300 GB should not hang the computer or take 3 hours.
What kind of disk is F:? Is it an external disk (USB or such, and if so, what speed and kind)? Is it a network drive? Is it another local disk in the computer (SSD or HDD)?
Are you using an antivirus or firewall other than the default, or any sort of other monitoring software? What I suspect is happening here is that you have an antivirus intercepting Git's operations and scanning the files for viruses, making everything really slow, and then at some point a bug occurs in the antivirus (which may have a kernel driver) and then things hang. This is probably made worse if F: is an external drive or network drive.
If you are, can you try to completely uninstall that software and reboot, and then try again?
--
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA
---TAW--- it's SSD, actually NVme, and the PC is 128GB ram 64 core very fast.
---TAW--- Both drives are local SSD drives, the working directory on D: and the repo on F:.
---TAW--- the 3 hour thing is not a problem as such (it's a little frustrating that git is single threaded, but regardless, this is not the issue I am concerned with)
---TAW--- it's only 3 hours once, on the very first git add when I create the repo
---TAW--- I can live with that, I was just giving context.
---TAW---
---TAW--- The real issue is that it does a "very bad hang and mess up of the OS" if the repo is separate from the working directory.
---TAW--- In my case it happens to be a separate drive, not sure if that is relevant, I didn't try a separate folder on the same drive.
---TAW---
---TAW--- There's anti-virus (SentinelOne) but we're very familiar with how that works, I don't think that is the issue, and on-demand scanning is disabled anyway.
---TAW--- no firewall locally, our network obviously has firewall for the entire company network, but the workstations don't have individual firewall enabled.
---TAW--- Again, I'm not complaining about the speed, (that was just for context, and can be discussed as a separate issue if needed)
---TAW--- it's the hang and break the OS in a really nasty way that I am concerned with.
---TAW---
---TAW--- It's not possible to uninstall the anti-virus SW, company policy and I don't have permissions for that level of configuration.
---TAW--- Our current solution (perforce) manages the same source files and does not have any interaction with the anti-virus
---TAW---We're careful to tell the anti-virus to ignore certain folders, and not to do on-demand scanning on those drives anyway.
---TAW--- That's one of the reasons we have separate drives (c: is protected a lot more than d: which is just the "work folders" for example.
---TAW---
---TAW--- I expected that other people would have had this issue already, but it sounds like you've never heard of it, so maybe something odd
---TAW--- about our particular configuration? But I don't know what, except that:
---TAW--- : it's a large project
---TAW--- : it contains binary as well as text files
---TAW--- : I am trying to use 2 different local drives
---TAW--- : I am using windows, sorry can't help that, we are forced to develop using windows tools.
next prev parent reply other threads:[~2023-05-16 22:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 17:54 git hangs with --separate-git-dir Tim Walter (Visual Concepts)
2023-05-16 21:30 ` brian m. carlson
2023-05-16 21:55 ` Tim Walter (Visual Concepts) [this message]
2023-05-17 1:20 ` brian m. carlson
2023-05-17 7:11 ` Erik Cervin Edin
2023-05-17 16:31 ` Tim Walter (Visual Concepts)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BY5PR14MB36541924E1E6E5E912AFE0C2A5799@BY5PR14MB3654.namprd14.prod.outlook.com \
--to=twalter@vcentertainment.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).