# Algorand Indexer Storing Data in Wrong Drive

**URL:** <https://forum.algorand.co/t/algorand-indexer-storing-data-in-wrong-drive/6466>\
**Category:** General\
**Tags:** noderunner\
**Created:** [April 12, 2022, 10:08pm UTC](https://forum.algorand.co/t/algorand-indexer-storing-data-in-wrong-drive/6466 "2022-04-12T22:08:36Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![victorsh](https://avatars.discourse-cdn.com/v4/letter/v/3d9bf3/32.png) [@victorsh](https://forum.algorand.co/u/victorsh)\
**Post date:** [April 13, 2022, 1:55am UTC](https://forum.algorand.co/t/algorand-indexer-storing-data-in-wrong-drive/6466/3 "2022-04-13T01:55:53Z")

</div>

That’s very odd, can postgres store data to a different location even though show directory is pointing to the right location? The image below is pointed to the correct drive. I’ve also deleted the original postgres directory to ensure that it’s note writing there. To make sure algod isn’t writing to the original directory I’ve also deleted that folder in /var/lib/algorand  
 ![Screen Shot 2022-04-12 at 6.54.06 PM](https://us1.discourse-cdn.com/flex016/uploads/algorand/original/2X/7/7a47ce5bbeddb311c29d64f74fb660c7903fe6f3.png)

---

_[View the full topic](https://forum.algorand.co/t/algorand-indexer-storing-data-in-wrong-drive/6466)._