Unable to create shared content manager: error loading indexes

General
1

Hi

How do I solve this issue?

kopia maintenance run throws these errors.

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


kopia --version
0.18.2 build: c70f1a1c1164ee8676f85f9a1cea6de0a782a3ae from: kopia/kopia
2

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?

2 Likes
3

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

4

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.

1 Like
5

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.