# Farming preparation

**URL:** <https://forum.storj.io/t/farming-preparation/28209>\
**Category:** Node Operators\
**Tags:** hardware\
**Created:** [October 11, 2024, 3:33am UTC](https://forum.storj.io/t/farming-preparation/28209 "2024-10-11T03:33:33Z")\
**Posts on this page:** 1\
**Showing post:** 36

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [October 12, 2024, 4:09am UTC](https://forum.storj.io/t/farming-preparation/28209/36 "2024-10-12T04:09:51Z")

</div>

> [@Churchillhuang](#):
>
> The network trying to avoiding the copies of the data storage in a same physical location, if 80 copies are stored in one physical location, It’s nonsense.

We do not use replication, we use a Reed-Solomon erasure codes, so no copies, each piece is unique. You do not need to keep 80 pieces of the segment to make it unavailable. Holding 52 pieces would be enough to make the segment unavailable. Sometimes even less, because the repair will start when the minimum threshold is passed, so 65-28=37 pieces could be enough.  
Numbers are various, depending on used R-S settings, they now can be dynamic. So, numbers above are valid for the default schema:

> [@Updates on Test Data](https://forum.storj.io/t/updates-on-test-data/26034/290):
>
> Our current RS setting is `29/35/65/110` without the repair override. 65/29=2.25 expansion factor. 110/29=3.8 for bandwidth. It is up to 3.8 depending on how much traffic long tail can cancel out.

---

_[View the full topic](https://forum.storj.io/t/farming-preparation/28209)._