Hey, On 2022-04-18 at 07:47:07, Attila Csosz wrote: > 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. There's nothing that Git should be able to do as a normal operating system that causes disk errors. If you're seeing those kinds of errors, the likelihood is that your disk is bad and you need to replace it. Do note that if you're storing your data in a directory managed by a cloud syncing service (e.g., Dropbox or OneDrive), then it is known that those file systems corrupt Git repositories and you shouldn't use them with Git. That's due to the way they sync data. However, if this is a regular file system (e.g., NTFS), then Git shouldn't be able to cause disk problems, and if it could, that would be a serious defect in Windows, so it's almost certainly going to be a hardware problem. -- brian m. carlson (he/him or they/them) Toronto, Ontario, CA
Attachment:
signature.asc
Description: PGP signature
