Please check this link also https://github.community/t/what-could-be-the-reason-my-git-repositories-keep-getting-corrupted-broken/184711 You can found many link on web on 'git corrupted repository'. In my opinion when a git repository is corrupted on Windows there is a good chance to HDD errors. I suggest also run intensive test on Windows (run a bat file commiting and pushing to a bare directory type repository). Check your HDD healthy status after 10-20 run of 'git push'. My git software is come form 'git-scm.com' and I'm using TortoiseGit. My git software is up to date. Last time my laptop HDD is crashed loosing sensitive datas. I will never push to a local repo I'm using online repo-s like github. /// fsutil fsinfo volumeinfo e: Volume Name : Seagate Backup Plus Drive Volume Serial Number : <removed by hand> Max Component Length : 255 File System Name : NTFS Is ReadWrite Not Thinly-Provisioned Supports Case-sensitive filenames Preserves Case of filenames Supports Unicode in filenames Preserves & Enforces ACL's Supports file-based Compression Supports Disk Quotas Supports Sparse files Supports Reparse Points Returns Handle Close Result Information Supports POSIX-style Unlink and Rename Supports Object Identifiers Supports Encrypted File System Supports Named Streams Supports Transactions Supports Hard Links Supports Extended Attributes Supports Open By FileID Supports USN Journal /// Maybe this email not reaching the main mailing list I'm somehow blacklisted. Attila On Thu, Apr 21, 2022 at 12:54 AM Neeraj Singh <nksingh85@xxxxxxxxx> wrote: > > On 4/18/2022 8:52 PM, Attila Csosz wrote: > > I've experienced the problem at least 3 different external disk. > > I'm not using cloud syncing service (e.g., Dropbox or OneDrive) for git. > > > > Attila > > > Hi Attila, > Could you please share a bit more information about the disks that are > being corrupted and the specific error messages you're seeing? > > What is the underlying storage type (e.g. USB key, external hard drive, > etc)? Also, which filesystem is the drive formatted as? > > Could you please save one instance of a volume in the corrupted state so > that we can consider further investigations? > > I believe the output of "fsutil fsinfo volumeinfo <drive letter>" and > "fsutil fsinfo drivetype <drive letter>" should give us some useful info > about the volume that's being corrupted. > > Thanks, > Neeraj Singh, > Windows FileSystem Dev
