# Remote: Aborting due to possible repository corruption

**URL:** <https://forum.gitea.com/t/remote-aborting-due-to-possible-repository-corruption/6617>\
**Category:** Install/Maintain/Configure\
**Created:** [January 27, 2023, 12:12am UTC](https://forum.gitea.com/t/remote-aborting-due-to-possible-repository-corruption/6617 "2023-01-27T00:12:00Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jake](https://avatars.discourse-cdn.com/v4/letter/j/f475e1/32.png) [@jake](https://forum.gitea.com/u/jake)\
**Post date:** [January 27, 2023, 11:41am UTC](https://forum.gitea.com/t/remote-aborting-due-to-possible-repository-corruption/6617/2 "2023-01-27T11:41:06Z")

</div>

To apply the fix from StackOverflow post, you can either edit `[repository.root]/user/repo.git/config` for just the one large repo or edit `/var/lib/gitea/.gitconfig` for all repositories and add:

```auto
[pack]
         windowMemory = 100m
         SizeLimit = 100m
         threads = 1

```

Alternatively, add `window = 0` instead of windowMemory, SizeLimit, … to disable packing entirely, but note that cloning will be less efficient.

---

_[View the full topic](https://forum.gitea.com/t/remote-aborting-due-to-possible-repository-corruption/6617)._