## TL;DR

Run Weaviate with its data dir on local disk (for example /var/lib/weaviate). Issue weaviate/weaviate#3153 (closed, 18 comments): Dear team we updated to v1.19.8 and now we are having a runtime error similar to a previous issue #1897 that was fixed before.

## Steps

1. Issue weaviate/weaviate#3153 (closed, 18 comments): Dear team

2. we updated to v1.19.8 and now we are having a runtime error similar to a previous issue #1897 that was fixed before.
Can you please take a look at this?

3. Instance running in Azure, mounted file share.

4. `{"action":"startup","level":"debug","msg":"created startup context, nothing done so far","startup_time_left":"59m59.998647187s","time":"2023-06-18T13:38:59Z"}
{"action":"startup","default_vectorizer_module":"text2vec-openai","level":"info","msg":"the default vectorizer modules is set to \"text2vec-openai\", as a result all new schema classes without an...

5. The panic comes from Weaviate's data files living directly on an Azure File Share (SMB) mount. The confirmed operational workaround from a user: keep the active data on local storage and sync it to the file share yourself.

6. Run Weaviate with its data dir on local disk (for example `/var/lib/weaviate`).
2. Mount the file share elsewhere (for example `/mnt/weaviate_data`) and run a periodic `rsync -av --delete /var/lib/weaviate/ /mnt/weaviate_data/` (the reporter used every 5 minutes).
3. On container startup, restore from the share into the local data dir before Weaviate starts.

7. Caveat: this is crash-unsafe between syncs; anything written since the last sync is lost on a crash. Weaviate also later added checksum validation on segment files, but the SMB-mount panic itself had no in-place fix in the thread.

## When to use

You are seeing this: Can you please take a look at this? Use this skill when you run into "panic: runtime error: slice bounds out of range [:752185] with capacity 186278".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: v1.19.8. If you are on something much newer or older, the details may have shifted.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

## Edge cases

- Caveat: this is crash-unsafe between syncs; anything written since the last sync is lost on a crash.
