W E K A
4.4
4.4
  • WEKA v4.4 documentation
    • Documentation revision history
  • WEKA System Overview
    • Introduction
      • WEKA system functionality features
      • Converged WEKA system deployment
      • Redundancy optimization in WEKA
    • SSD capacity management
    • Filesystems, object stores, and filesystem groups
    • WEKA networking
    • Data lifecycle management
    • WEKA client and mount modes
    • WEKA containers architecture overview
    • Glossary
  • Planning and Installation
    • Prerequisites and compatibility
    • WEKA cluster installation on bare metal servers
      • Plan the WEKA system hardware requirements
      • Obtain the WEKA installation packages
      • Install the WEKA cluster using the WMS with WSA
      • Install the WEKA cluster using the WSA
      • Manually install OS and WEKA on servers
      • Manually prepare the system for WEKA configuration
        • Broadcom adapter setup for WEKA system
        • Enable the SR-IOV
      • Configure the WEKA cluster using the WEKA Configurator
      • Manually configure the WEKA cluster using the resources generator
        • VLAN tagging in the WEKA system
      • Perform post-configuration procedures
      • Add clients to an on-premises WEKA cluster
    • WEKA Cloud Deployment Manager Web (CDM Web) User Guide
    • WEKA Cloud Deployment Manager Local (CDM Local) User Guide
    • WEKA installation on AWS
      • WEKA installation on AWS using Terraform
        • Terraform-AWS-WEKA module description
        • Deployment on AWS using Terraform
        • Required services and supported regions
        • Supported EC2 instance types using Terraform
        • WEKA cluster auto-scaling in AWS
        • Detailed deployment tutorial: WEKA on AWS using Terraform
      • WEKA installation on AWS using the Cloud Formation
        • Self-service portal
        • CloudFormation template generator
        • Deployment types
        • AWS Outposts deployment
        • Supported EC2 instance types using Cloud Formation
        • Add clients to a WEKA cluster on AWS
        • Auto scaling group
        • Troubleshooting
    • WEKA installation on Azure
      • Azure-WEKA deployment Terraform package description
      • Deployment on Azure using Terraform
      • Required services and supported regions
      • Supported virtual machine types
      • Auto-scale virtual machines in Azure
      • Add clients to a WEKA cluster on Azure
      • Troubleshooting
      • Detailed deployment tutorial: WEKA on Azure using Terraform
    • WEKA installation on GCP
      • WEKA project description
      • GCP-WEKA deployment Terraform package description
      • Deployment on GCP using Terraform
      • Required services and supported regions
      • Supported machine types and storage
      • Auto-scale instances in GCP
      • Add clients to a WEKA cluster on GCP
      • Troubleshooting
      • Detailed deployment tutorial: WEKA on GCP using Terraform
      • Google Kubernetes Engine and WEKA over POSIX deployment
    • WEKA installation on OCI
  • Getting Started with WEKA
    • Manage the system using the WEKA GUI
    • Manage the system using the WEKA CLI
      • WEKA CLI hierarchy
      • CLI reference guide
    • Run first IOs with WEKA filesystem
    • Getting started with WEKA REST API
    • WEKA REST API and equivalent CLI commands
  • Performance
    • WEKA performance tests
      • Test environment details
  • WEKA Filesystems & Object Stores
    • Manage object stores
      • Manage object stores using the GUI
      • Manage object stores using the CLI
    • Manage filesystem groups
      • Manage filesystem groups using the GUI
      • Manage filesystem groups using the CLI
    • Manage filesystems
      • Manage filesystems using the GUI
      • Manage filesystems using the CLI
    • Attach or detach object store buckets
      • Attach or detach object store bucket using the GUI
      • Attach or detach object store buckets using the CLI
    • Advanced data lifecycle management
      • Advanced time-based policies for data storage location
      • Data management in tiered filesystems
      • Transition between tiered and SSD-only filesystems
      • Manual fetch and release of data
    • Mount filesystems
      • Mount filesystems from Single Client to Multiple Clusters (SCMC)
      • Manage authentication across multiple clusters with connection profiles
    • Snapshots
      • Manage snapshots using the GUI
      • Manage snapshots using the CLI
    • Snap-To-Object
      • Manage Snap-To-Object using the GUI
      • Manage Snap-To-Object using the CLI
    • Snapshot policies
      • Manage snapshot policies using the GUI
      • Manage snapshot policies using the CLI
    • Quota management
      • Manage quotas using the GUI
      • Manage quotas using the CLI
  • Additional Protocols
    • Additional protocol containers
    • Manage the NFS protocol
      • Supported NFS client mount parameters
      • Manage NFS networking using the GUI
      • Manage NFS networking using the CLI
    • Manage the S3 protocol
      • S3 cluster management
        • Manage the S3 service using the GUI
        • Manage the S3 service using the CLI
      • S3 buckets management
        • Manage S3 buckets using the GUI
        • Manage S3 buckets using the CLI
      • S3 users and authentication
        • Manage S3 users and authentication using the CLI
        • Manage S3 service accounts using the CLI
      • S3 lifecycle rules management
        • Manage S3 lifecycle rules using the GUI
        • Manage S3 lifecycle rules using the CLI
      • Audit S3 APIs
        • Configure audit webhook using the GUI
        • Configure audit webhook using the CLI
        • Example: How to use Splunk to audit S3
        • Example: How to use S3 audit events for tracking and security
      • S3 supported APIs and limitations
      • S3 examples using boto3
      • Configure and use AWS CLI with WEKA S3 storage
    • Manage the SMB protocol
      • Manage SMB using the GUI
      • Manage SMB using the CLI
  • Security
    • WEKA security overview
    • Obtain authentication tokens
    • Manage token expiration
    • Manage account lockout threshold policy
    • Manage KMS
      • Manage KMS using GUI
      • Manage KMS using CLI
    • Manage TLS certificates
      • Manage TLS certificates using GUI
      • Manage TLS certificates using CLI
    • Manage Cross-Origin Resource Sharing
    • Manage CIDR-based security policies
    • Manage login banner
  • Secure cluster membership with join secret authentication
  • Licensing
    • License overview
    • Classic license
  • Operation Guide
    • Alerts
      • Manage alerts using the GUI
      • Manage alerts using the CLI
      • List of alerts and corrective actions
    • Events
      • Manage events using the GUI
      • Manage events using the CLI
      • List of events
    • Statistics
      • Manage statistics using the GUI
      • Manage statistics using the CLI
      • List of statistics
    • Insights
    • System congestion
    • User management
      • Manage users using the GUI
      • Manage users using the CLI
    • Organizations management
      • Manage organizations using the GUI
      • Manage organizations using the CLI
      • Mount authentication for organization filesystems
    • Expand and shrink cluster resources
      • Add a backend server
      • Expand specific resources of a container
      • Shrink a cluster
    • Background tasks
      • Set up a Data Services container for background tasks
      • Manage background tasks using the GUI
      • Manage background tasks using the CLI
    • Upgrade WEKA versions
    • Manage WEKA drivers
  • Monitor the WEKA Cluster
    • Deploy monitoring tools using the WEKA Management Station (WMS)
    • WEKA Home - The WEKA support cloud
      • Local WEKA Home overview
      • Deploy Local WEKA Home v3.0 or higher
      • Deploy Local WEKA Home v2.x
      • Explore cluster insights
      • Explore performance statistics in Grafana
      • Manage alerts and integrations
      • Enforce security and compliance
      • Optimize support and data management
      • Export cluster metrics to Prometheus
    • Set up WEKAmon for external monitoring
    • Set up the SnapTool external snapshots manager
  • Kubernetes
    • Composable clusters for multi-tenancy in Kubernetes
    • WEKA Operator deployment
    • WEKA Operator day-2 operations
  • WEKApod
    • WEKApod Data Platform Appliance overview
    • WEKApod servers overview
    • Rack installation
    • WEKApod initial system setup and configuration
    • WEKApod support process
  • AWS Solutions
    • Amazon SageMaker HyperPod and WEKA Integrations
      • Deploy a new Amazon SageMaker HyperPod cluster with WEKA
      • Add WEKA to an existing Amazon SageMaker HyperPod cluster
    • AWS ParallelCluster and WEKA Integration
  • Azure Solutions
    • Azure CycleCloud for SLURM and WEKA Integration
  • Best Practice Guides
    • WEKA and Slurm integration
      • Avoid conflicting CPU allocations
    • Storage expansion best practice
  • Support
    • Get support for your WEKA system
    • Diagnostics management
      • Traces management
        • Manage traces using the GUI
        • Manage traces using the CLI
      • Protocols debug level management
        • Manage protocols debug level using the GUI
        • Manage protocols debug level using the CLI
      • Diagnostics data management
  • Appendices
    • WEKA CSI Plugin
      • Deployment
      • Storage class configurations
      • Tailor your storage class configuration with mount options
      • Dynamic and static provisioning
      • Launch an application using WEKA as the POD's storage
      • Add SELinux support
      • NFS transport failback
      • Upgrade legacy persistent volumes for capacity enforcement
      • Troubleshooting
    • Convert cluster to multi-container backend
    • Create a client image
    • Update WMS and WSA
    • BIOS tool
Powered by GitBook
On this page
  • Set default quota
  • Set directory quota
  • List directory quotas/default quotas
  • Unset default quota
  • Reset directory quota
  1. WEKA Filesystems & Object Stores
  2. Quota management

Manage quotas using the CLI

This page describes how to manage quotas using the CLI.

PreviousManage quotas using the GUINextAdditional protocol containers

Last updated 2 months ago

Using the CLI, you can:

Set default quota

Command: weka fs quota set-default

Before using this command, ensure the following requirements are met:

  • A mount point to the relevant filesystem is set.

  • Deploy at least one Data Services container before setting any quotas. If not running, quota operations defaults to single-process mode, potentially causing CLI to hang for extended periods. See Set up a Data Services container for background tasks.

Default quotas apply to newly created subdirectories, not the directory or existing children.

Use the following command to set a default quota of a directory:

weka fs quota set-default <path> [--soft soft] [--hard hard] [--grace grace] [--owner owner]

Parameters

Name
Value
Default

path*

Path to the directory to set the quota. The relevant filesystem must be mounted when setting the quota.

​

soft

Soft quota limit. Exceeding this number is displayed as an exceeded quota, but it is not enforced until the grace period is over. The capacity can be in decimal or binary units. Format: 1GB, 1TB, 1GiB, 1TiB, unlimited

unlimited

hard

Hard quota limit. Exceeding this number does not allow more writes before clearing some space in the directory. The capacity can be in decimal or binary units. Format: 1GB, 1TB, 1GiB, 1TiB, unlimited

unlimited

grace

Specify the grace period before the soft limit is treated as a hard limit. Format: 1d, 1w, unlimited

unlimited

owner

A unique string identifying the directory owner (can be a name, email, slack ID, etc.) This owner will be shown in the quota report and can be notified upon exceeding the quota. Supports up to 48 characters.

  • To set advisory only quotas, use a soft quota limit without setting a grace period.

  • When hard and soft quotas exist, setting the value of one of them to 0 clears this quota.

Set directory quota

Command: weka fs quota set

Before using the commands, verify that at least one Data Services container is set to enable the command to run the QUOTA_COLORING task in the background. For details, see Set up a Data Services container for background tasks.

Use the following command to set a directory quota:

weka fs quota set <path> [--soft soft] [--hard hard] [--grace grace] [--owner owner] [--file-system file-system] [--snap-name snap-name] [--color color]

Parameters

Name
Value
Default

path*

Path to the directory to set the quota. The relevant filesystem must be mounted when setting the quota.

​

soft

Soft quota limit. Exceeding this number is displayed as an exceeded quota, but it is not enforced until the grace period is over. The capacity can be in decimal or binary units. Format: 1GB, 1TB, 1GiB, 1TiB, unlimited

unlimited

hard

Hard quota limit. Exceeding this number does not allow more writes before clearing some space in the directory. The capacity can be in decimal or binary units. Format: 1GB, 1TB, 1GiB, 1TiB, unlimited

unlimited

grace

Specify the grace period before the soft limit is treated as a hard limit. Format: 1d, 1w, unlimited

unlimited

owner

A unique string identifying the directory owner (can be a name, email, slack ID, etc.) This owner will be shown in the quota report and can be notified upon exceeding the quota. Supports up to 48 characters.

file-system

Filesystem name. Use this parameter to set a quota outside the mount point.

snap-name

Name of the writable snapshot. Use this parameter to set a quota outside the mount point.

List directory quotas/default quotas

Command: weka fs quota list / weka fs quota list-default

Use the following command to list the directory quotas (by default, only exceeding quotas are listed) :

weka fs quota list [fs-name] [--snap-name snap-name] [--path path] [--under under] [--over over] [--quick] [--all]

Parameters

Name
Value
Default

fs-name*

Filesystem name. Use this parameter to display a quota report only on the specified filesystem.

All filesystems

snap-name

Displays the quota report from the time of the snapshot. It must be a valid snapshot name and be given along with the corresponding fs-name.

path

Path to a directory. Shows quota report only on the specified directory. The relevant filesystem must be mounted in the server running the query.

under

A path to a directory under a wekafs mount. The relevant filesystem must be mounted in the server running the query.

over

Shows only quotas over this percentage of usage. Possible values: 0-100

quick

Do not resolve inode to a path. Provides quicker results if the report contains many entries.

False

all

Shows all the quotas, not just the exceeding ones.

False

Use the following command to list the directory default quotas:

weka fs quota list-default [fs-name] [--snap-name snap-name] [--path path]

Parameters

Name
Value
Default

fs-name

Filesystem name. Use this parameter to display the default quotas only on the specified filesystem.

All filesystems

snap-name

Displays the default quotas from the time of the snapshot. It must be a valid snapshot name and be given along with the corresponding fs-name.

path

Path to a directory. Shows the default quotas report only on the specified directory. The relevant filesystem must be mounted in the server running the query.

Unset default quota

Command: weka fs quota unset-default

Use the following command to unset a default quota of a directory:

weka fs quota unset-default <path>

Parameters

Name
Value

path*

Path to the directory to set the quota. The relevant filesystem must be mounted when setting the quota.

Reset directory quota

Command: weka fs quota reset

Use the following command to reset a directory quota:

weka fs quota reset <path>

Parameters

Name
Value

path*

Path to the directory to unset the quota. The relevant filesystem must be mounted when setting the quota.

Set default quota
Set directory quota
List directory quotas/default quotas
Unset default quota
Reset directory quota