From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: "Tim Walter (Visual Concepts)" <twalter@vcentertainment.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git hangs with --separate-git-dir
Date: Tue, 16 May 2023 21:30:43 +0000 [thread overview]
Message-ID: <ZGP2AzYJSLpI4kGN@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <BY5PR14MB36544D63ECEAB9954C14407FA5799@BY5PR14MB3654.namprd14.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1894 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2023-05-16 21:30 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 [this message]
2023-05-16 21:55 ` Tim Walter (Visual Concepts)
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=ZGP2AzYJSLpI4kGN@tapette.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=twalter@vcentertainment.com \
/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).