# Unable to create shared content manager: error loading indexes

**URL:** https://kopia.discourse.group/t/unable-to-create-shared-content-manager-error-loading-indexes/3553
**Category:** General
**Created:** [December 17, 2024, 6:54pm UTC](https://kopia.discourse.group/t/unable-to-create-shared-content-manager-error-loading-indexes/3553 "2024-12-17T18:54:41Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![wayland](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/wayland/32/268_2.png) [@wayland](https://kopia.discourse.group/u/wayland)
#### Post date: [December 17, 2024, 6:54pm UTC](https://kopia.discourse.group/t/unable-to-create-shared-content-manager-error-loading-indexes/3553/1 "2024-12-17T18:54:41Z")

</div>

Hi

How do I solve this issue?

`kopia maintenance run` throws these errors.

```auto
ERROR failed to open repository: unable to create shared content manager: error loading indexes: error downloading indexes: error loading index blob xn125_7b9b99120863db77e1b939b19a8d9095-s97d5472c8f703c8912f-c1: getContent: unable to complete 

GetBlobFromPath:/media/KOPIA/XXXX/xn1/25_/7b9b99120863db77e1b939b19a8d9095-s97d5472c8f703c8912f-c1.f despite 10 retries: read 

/media/KOPIA/XXXX//xn1/25_/7b9b99120863db77e1b939b19a8d9095-s97d5472c8f703c8912f-c1.f: value too large for defined data typ

```

```auto
kopia --version
0.18.2 build: c70f1a1c1164ee8676f85f9a1cea6de0a782a3ae from: kopia/kopia

```

---

<div class="post-metadata">

### Author: ![kapitainsky](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/kapitainsky/32/535_2.png) [@kapitainsky](https://kopia.discourse.group/u/kapitainsky)
#### Post date: [December 17, 2024, 10:44pm UTC](https://kopia.discourse.group/t/unable-to-create-shared-content-manager-error-loading-indexes/3553/2 "2024-12-17T22:44:48Z")

</div>

Fix access to your backup location maybe?

From snippet info you posted it looks like kopia has issues accessing content in ` /media/KOPIA/...`

Can be multiple reasons. Not enough free space. Permissions issue. Corrupted data.

What it is? SMB mount? or external disk? what filesystem?

---

<div class="post-metadata">

### Author: ![wayland](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/wayland/32/268_2.png) [@wayland](https://kopia.discourse.group/u/wayland)
#### Post date: [December 17, 2024, 11:17pm UTC](https://kopia.discourse.group/t/unable-to-create-shared-content-manager-error-loading-indexes/3553/3 "2024-12-17T23:17:14Z")

</div>

Thanks. It is NTFS mounted on a Linux system. The CLI is accessing it directly. The suer has full access. I will investigate it.

---

<div class="post-metadata">

### Author: ![kapitainsky](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/kapitainsky/32/535_2.png) [@kapitainsky](https://kopia.discourse.group/u/kapitainsky)
#### Post date: [December 18, 2024, 7:11am UTC](https://kopia.discourse.group/t/unable-to-create-shared-content-manager-error-loading-indexes/3553/4 "2024-12-18T07:11:15Z")

</div>

> [@wayland](#):
>
> Thanks. It is NTFS mounted on a Linux system

Don’t. I have seen multiple disaster stories with such configuration (not only with kopia). NTFS support on Linux is far from perfect - it is reverse engineered solution for close source filesystem.

IMO Iit can be used to read some data if needed (and I would not count on this neither in mission critical solutions).

Use some filesystem fully supported by Linux (ext4, btrfs etc.) and you won’t see such issues.

---

<div class="post-metadata">

### Author: ![wayland](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/wayland/32/268_2.png) [@wayland](https://kopia.discourse.group/u/wayland)
#### Post date: [December 18, 2024, 5:58pm UTC](https://kopia.discourse.group/t/unable-to-create-shared-content-manager-error-loading-indexes/3553/5 "2024-12-18T17:58:07Z")

</div>

Thanks but that is too late for me given I already have like 7TB of backup o that drive, I will keep it in mind for the next drive.
