# Dvc cache content

**URL:** <https://discuss.dvc.org/t/dvc-cache-content/1749>\
**Category:** Questions\
**Created:** [September 1, 2023, 10:27am UTC](https://discuss.dvc.org/t/dvc-cache-content/1749 "2023-09-01T10:27:10Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![run45](https://avatars.discourse-cdn.com/v4/letter/r/f6c823/32.png) [@run45](https://discuss.dvc.org/u/run45)\
**Post date:** [September 1, 2023, 10:27am UTC](https://discuss.dvc.org/t/dvc-cache-content/1749/1 "2023-09-01T10:27:10Z")

</div>

So previously when I looked into the dvc cache I found directories 00 to ff which corresponded to the md5 starting values of my files. But now I see another directory called files/md5 which again has 00 to ff directories in it that correspond to md5 values of different files. Does anyone know why there is now a files/md5 directory and why not all md5 related directories live in the root dir of the dvc cache ?

I am not saying this is causing any problem but I was just surprised to see this today.

---

<div class="post-metadata">

**Author:** ![daavoo](https://avatars.discourse-cdn.com/v4/letter/d/b4bc9f/32.png) [@daavoo](https://discuss.dvc.org/u/daavoo)\
**Post date:** [September 1, 2023, 10:40am UTC](https://discuss.dvc.org/t/dvc-cache-content/1749/2 "2023-09-01T10:40:30Z")

</div>

This change in the structure of the cache was shipped as part of DVC 3.0 . See:

[Upgrading to DVC 3.0 | Data Version Control · DVC](https://dvc.org/doc/user-guide/upgrade#file-hashing-changes)

---

<div class="post-metadata">

**Author:** ![run45](https://avatars.discourse-cdn.com/v4/letter/r/f6c823/32.png) [@run45](https://discuss.dvc.org/u/run45)\
**Post date:** [September 1, 2023, 10:48am UTC](https://discuss.dvc.org/t/dvc-cache-content/1749/3 "2023-09-01T10:48:51Z")

</div>

thanx. that was exactly the info I was after!! 😀

---

<div class="post-metadata">

**Author:** ![run45](https://avatars.discourse-cdn.com/v4/letter/r/f6c823/32.png) [@run45](https://discuss.dvc.org/u/run45)\
**Post date:** [September 1, 2023, 12:17pm UTC](https://discuss.dvc.org/t/dvc-cache-content/1749/4 "2023-09-01T12:17:48Z")

</div>

not sure if I should open another issue or not (last one got hidden by AI spam filter 🙂 … fingers crossed that gets released soon 😀 )

So I read in the documentation that by default no de-duplication for 2.0/3.0 cache entries happens but that  
dvc cache migrate  
would help with this.

I checked now on the remote and noticed the same duplicate files. What is the right way to remove duplicates on the remote side of things ?