DGrid has not published instructions for “volume 0” or explicit metadata volume allocation like StorageGRID or other object storage systems, so no official procedure exists yet for configuring a separate metadata volume on DGrid nodes.
What DGrid docs describe:
- GridVM containers running models.
- Logging of requests (inputs, outputs, timestamps, PoQ data) archivable to DStorage.
What they do not mention:
- A “volume 0” concept.
- A configurable “metadata reserved space” setting per node, like in NetApp StorageGRID.
Currently, running a DGrid node means using a single SSD/NVMe volume (e.g., / or /data) large enough for:
- OS Docker/containers.
- Model weights.
- Logs and metadata.
No requirement exists to split storage into a special “volume 0” for metadata or set metadata quotas like in StorageGRID.
Practical recommendation (until official specs):
Use one main SSD/NVMe data volume (e.g., 512 GB–1 TB) for node data.
Optionally, for advanced users wanting separation:
Mount /models (for weights) and /var/lib/dgrid (or future documented paths for logs/metadata) on separate partitions/drives.
This is an operational choice, not a DGrid requirement.
For updates on formalized node packaging, check
docs.dgrid.ai for any official volume layout or metadata reservation details.