Introduction
VAST is the underlying platform behind Crusoe's shared NFS storage volumes, and it's common for teams to ask about controlling how much capacity individual users or directories consume on a shared mount. This FAQ covers what's currently possible for quota management on Crusoe-provisioned VAST volumes and what to do if per-user quotas are a requirement for your workload.
Question 1: Can I configure quotas on user directories within a shared VAST volume?
Answer: Not as a self-service option today. VAST Data's platform includes quota management capabilities at the protocol level (see VAST's quota documentation for how the feature works generally), but Crusoe has not exposed or qualified this configuration for customers on shared volumes.
ℹ️ Note: This is an unreleased capability on Crusoe's platform, not a limitation of VAST itself. If per-user quota enforcement is a requirement for your workload, open a support ticket describing your use case so it can be routed to the Product/Storage team for evaluation.
Question 2: What are my options for limiting storage consumption today without native quotas?
Answer: A couple of patterns work around the lack of in-place quotas on a single shared mount.
- Provision separate volumes per team or per user, each sized to the capacity you want that group to consume, rather than relying on sub-directory limits within one shared volume.
- Monitor usage proactively with standard tools like
duorncduagainst mount points, and alert when a directory approaches a threshold you define.
Question 3: Does this affect all Crusoe storage types, or just VAST?
Answer: This FAQ addresses shared VAST NFS volumes specifically. If you're using a different storage backend and need quota behavior, open a support ticket with details on the storage type and use case so it can be assessed separately.
Question 4: Will per-user directory quotas be supported in the future?
Answer: There's no committed timeline. Feature requests like this are routed to the Storage Product and Engineering teams for evaluation, and prioritization depends on factors like urgency and how many customers need it. If you have a use case for this, opening a ticket with details on scale, urgency, and expected quota sizes helps the team make that call.
💡 Tip: The more specific your use case (number of users, expected data volumes, how critical the limit is to your workflow), the easier it is for the team to evaluate feasibility and priority.