git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Attila Csosz <csosza@designsoftware.com>
To: git@vger.kernel.org
Subject: Git bug report - disk errors on Windows after push
Date: Mon, 18 Apr 2022 09:47:07 +0200	[thread overview]
Message-ID: <4026b85f-8cae-bcca-af14-e886e80725d4@designsoftware.com> (raw)

Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.

What did you do before the bug happened? (Steps to reproduce your issue)
Pushing to a directory directly.

What did you expect to happen? (Expected behavior)
Good behavior

What happened instead? (Actual behavior)
Disk errors. After pushing to a directory (my origin field is C:\Work 
for example) the git repository will be corrupted.
Moreover causing disk errors not only in the target git bare repository. 
I've loosed some other files.
Cannot be reproduced exactly. However I have decided to report this 
problem.
I've experienced this problem for several years.

What's different between what you expected and what actually happened?
Described.

Anything else you want to add:

Please review the rest of the bug report below.
You can delete any lines you don't wish to share.


[System Info]
git version:
git version 2.31.1.windows.1
cpu: x86_64
built from commit: c5f0be26a7e3846e3b6268d1c6c4800d838c6bbb
sizeof-long: 4
sizeof-size_t: 8
shell-path: /bin/sh
feature: fsmonitor--daemon
uname: Windows 10.0 19044
compiler info: gnuc: 10.2
libc info: no libc information available
$SHELL (typically, interactive shell): C:\Program Files\Git\usr\bin\bash.exe


[Enabled Hooks]



             reply	other threads:[~2022-04-18  8:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-18  7:47 Attila Csosz [this message]
2022-04-18 17:37 ` Git bug report - disk errors on Windows after push brian m. carlson
2022-04-19  3:52   ` Attila Csosz
2022-04-20 21:28     ` brian m. carlson
2022-04-20 22:54     ` Neeraj Singh
2022-04-21  2:29       ` Attila Csosz
2022-04-21 20:08         ` Neeraj Singh
2022-04-22  9:27   ` Ævar Arnfjörð Bjarmason
2022-04-22 15:04     ` Attila Csosz
2022-04-22 16:13     ` Junio C Hamano

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=4026b85f-8cae-bcca-af14-e886e80725d4@designsoftware.com \
    --to=csosza@designsoftware.com \
    --cc=git@vger.kernel.org \
    /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 NNTP newsgroup(s).