Update docs.json - #746
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
|
||
| ## Limitations | ||
|
|
||
| Global volumes use object-backed storage, not a POSIX file system. Review the following before using global volumes in production. |
There was a problem hiding this comment.
not a POSIX file system -> not a fully POSIX compliant file system
There was a problem hiding this comment.
Done — updated to "not a fully POSIX compliant file system." Pushed to this branch in commit 4053e32.
| Global volumes use object-backed storage, not a POSIX file system. Review the following before using global volumes in production. | ||
|
|
||
| - **Not suitable for training writes:** Writing large volumes of data such as checkpoints, logs, and activations to a global volume during training is not supported. Use a network volume for workloads that write frequently. | ||
| - **No POSIX semantics:** Global volumes do not support file locking, atomic rename, or hard links. Applications that depend on POSIX behavior may fail or produce unexpected results. |
There was a problem hiding this comment.
No POSIX semantics
-> Limited POSIX semantics
There was a problem hiding this comment.
Done — the label now reads "Limited POSIX semantics." Pushed to this branch in commit 4053e32.
| - **Not suitable for training writes:** Writing large volumes of data such as checkpoints, logs, and activations to a global volume during training is not supported. Use a network volume for workloads that write frequently. | ||
| - **No POSIX semantics:** Global volumes do not support file locking, atomic rename, or hard links. Applications that depend on POSIX behavior may fail or produce unexpected results. | ||
| - **No concurrent writes across Pods:** Multiple Pods writing to the same global volume concurrently can cause data corruption or overwrite conflicts. Use a network volume for shared mutable storage. | ||
| - **Object consistency:** Reads reflect the state of the volume at mount time. Updates made to the volume after the Pod starts may not be immediately visible inside the container. |
There was a problem hiding this comment.
Object consistency -> "Eventual consistency"
There was a problem hiding this comment.
Done — the label now reads "Eventual consistency." Pushed to this branch in commit 4053e32.
|
On it — applying the requested wording changes to |
|
Confirmed the wording against the file and I'm applying the requested edits to the "Limitations" section of |
- Reword POSIX file system phrasing to 'not a fully POSIX compliant file system' - Relabel 'No POSIX semantics' as 'Limited POSIX semantics' - Relabel 'Object consistency' as 'Eventual consistency' Applies inline review suggestions from murat-runpod on PR #746.
murat-runpod
left a comment
murat-runpod
left a comment
There was a problem hiding this comment.
Just need to update /workspace -> /workspace-global in 3 places, other than that looks good!
| 5. Click the volume dropdown and select your volume from the **Global volumes** section. | ||
| 6. Click **Deploy Pod**. | ||
|
|
||
| The volume mounts at `/workspace` inside the container. |
There was a problem hiding this comment.
Should be: /workspace-global
There was a problem hiding this comment.
Done — updated to /workspace-global in commit 5082c66, pushed to this branch.
| Once the Pod is running, your files are available at `/workspace`. You can verify this from the Pod's **Console** tab: | ||
|
|
||
| ```bash | ||
| ls /workspace |
There was a problem hiding this comment.
same here, /workspace-global
There was a problem hiding this comment.
Done — the ls command now uses /workspace-global in commit 5082c66, pushed to this branch.
|
|
||
| ## Access your files | ||
|
|
||
| Once the Pod is running, your files are available at `/workspace`. You can verify this from the Pod's **Console** tab: |
There was a problem hiding this comment.
and here: /workspace-global
There was a problem hiding this comment.
Done — updated to /workspace-global in commit 5082c66, pushed to this branch.
Apply reviewer suggestions (murat-runpod) on PR #746: global volumes mount at /workspace-global, not the default Pod /workspace path.
2 participants
No description provided.