You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Assign specific app volumes to dedicated storage #7665
NS8 primary storage works best with drives offering fast random access. However, some data-intensive applications (e.g. Samba, Mail, Nextcloud, backup destinations) require large archive space. To optimize resource usage, specific application volumes can be mounted on separate, large-capacity drives instead of consuming the primary storage.
Proposed solution
Developer: Allow module developers to define which volumes can use additional disks.
Sysadmin: Enable and manage additional disks on cluster nodes for application use.
Sysadmin: During app install, restore, or clone, allow selection of the node’s additional disk to host the app’s volume.
Alternative solution
Support additional filesystem mount points, making them available for applications.
Allow module developers to define a volume role. Matching between available mount points and volumes can be automatic or user-supervised.
Define data migration policy: existing data may be preserved, migrated, or trigger a fatal error, depending on the developer’s decision.
Activity
Merge pull request #978 from NethServer/feat-7665
fix(docs): clarify :z volume flag (#981)
feat: set org.nethserver.volumes label (#142)
feat: set org.nethserver.volumes label (#168)
DavidePrincipi commentedon Nov 14, 2025
In Testing Core 3.14.0-dev.3
Test case
/etc/nethserver/volumes.confaccording to https://nethserver.github.io/ns8-core/modules/volumes/ guidelines (direct edit, or byvolumectlhelper)mrmarkuz commentedon Nov 18, 2025
Test case verified
Extra test case "remove-module" verified
feat(remove-module): reclaim space from disks (#984)
DavidePrincipi commentedon Nov 18, 2025
Released
feat: Assign named volume to an additional disk (#202)