W E K A
4.1
4.1
  • WEKA v4.1 documentation
  • WEKA System Overview
    • About the WEKA system
    • SSD capacity management
    • Filesystems, object stores, and filesystem groups
    • WEKA networking
    • Data lifecycle management
    • WEKA client and mount modes
    • WEKA containers architecture overview
    • Glossary
  • Getting Started with WEKA
    • Quick installation guide
    • Manage the system using the WEKA CLI
    • Manage the system using the WEKA GUI
    • Run first IOs with WEKA filesystem
    • Getting started with WEKA REST API
  • Planning and Installation
    • Prerequisites for installation
    • WEKA installation on bare metal
      • Plan the WEKA system Installation
      • Prepare the system for WEKA software installation
        • Enable the SR-IOV
      • Obtain the WEKA software installation package
      • WEKA cluster installation
        • WEKA legacy system installation process
      • Add clients
    • WEKA installation on AWS
      • Self-service portal
      • CloudFormation template generator
      • Deployment types
      • AWS outposts deployment
      • Supported EC2 instance types
      • Add clients
      • Auto scaling group
      • Troubleshooting
    • WEKA installation on Azure
    • WEKA installation on GCP
      • WEKA project description
      • Deployment on GCP using Terraform
      • GCP Terraform package description
      • Required services and supported regions
      • Supported machine types and storage
      • Auto-scale instances in GCP
      • Add clients
      • Troubleshooting
  • 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
    • 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
    • Quota management
      • Manage quotas using the GUI
      • Manage quotas using the CLI
  • Additional Protocols
    • Manage the NFS protocol
      • Supported NFS client mount options
      • Manage NFS networking using the GUI
      • Manage NFS networking using the CLI
    • Manage the SMB protocol
      • Manage SMB using the GUI
      • Manage SMB 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 rules information lifecycle management (ILM)
        • 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
      • S3 supported APIs and limitations
      • S3 examples using boto3
  • 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
    • System congestion
    • Security management
      • Obtain authentication tokens
      • KMS management
        • Manage KMS using the GUI
        • Manage KMS using the CLI
      • TLS certificate management
        • Manage the TLS certificate using the GUI
        • Manage the TLS certificate using the CLI
      • CA certificate management
        • Manage the CA certificate using the GUI
        • Manage the CA certificate using the CLI
      • Account lockout threshold policy management
        • Manage the account lockout threshold policy using GUI
        • Manage the account lockout threshold policy using CLI
      • Manage the login banner
        • Manage the login banner using the GUI
        • Manage the login banner using the CLI
    • 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 in a multiple containers architecture
      • Add a backend server in a legacy architecture
      • Expand specific resources of a container
      • Shrink a cluster
    • Background tasks
    • Upgrade WEKA versions
  • Billing & Licensing
    • License overview
    • Classic license
    • Pay-As-You-Go license
  • Support
    • Prerequisites and compatibility
    • 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
    • Weka Home - The WEKA support cloud
      • Local Weka Home overview
      • Local Weka Home deployment
      • Set the Local Weka Home to send alerts or events
      • Download the Usage Report or Analytics
  • Appendix
    • WEKA CSI Plugin
    • Set up the WEKAmon external monitoring
    • Set up the SnapTool external snapshots manager
  • REST API Reference Guide
Powered by GitBook
On this page
  • Set directory quota/default quota
  • List directory quotas/default quotas
  • Unsetting directory quota/default 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 GUINextManage the NFS protocol

Last updated 1 year ago

Using the CLI, you can:

Set directory quota/default quota

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

Before using the commands, verify that a mount point to the relevant filesystem is set.

Use the following commands to set a directory quota:

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

It is also possible to set a default quota on a directory. It does not account for this directory (or existing child directories) but will automatically set the quota on new directories created directly under it.

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

Type

Value

Limitations

Mandatory

Default

path

String

Path to the directory to set the quota on.

The relevant filesystem must be mounted when setting the quota.

Yes

​

soft

Number

Soft quota limit; Exceeding this number will be shown as exceeded quota but will not be enforced until the grace period is over.

Capacity in decimal or binary units, e.g.: 1GB, 1TB, 1GiB, 1TiB, unlimited

No

unlimited

hard

Number

Hard quota limit; Exceeding this number will not allow any more writes before clearing some space in the directory.

Capacity in decimal or binary units, e.g.: 1GB, 1TB, 1GiB, 1TiB, unlimited

No

unlimited

grace

Number

Specify the grace period before the soft limit is treated as a hard limit.

Format: 1d, 1w, unlimited

No

unlimited

owner

String

An opaque 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.

Up to 48 characters.

No

Notes:

  • Use a soft quota limit without setting a grace period to set advisory-only quotas.

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

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

Type

Value

Limitations

Mandatory

Default

fs-name

String

Shows quota report only on the specified filesystem.

A valid wekafs filesystem name.

No

All filesystems

snap-name

String

Shows the quota report from the time of the snapshot.

Must be a valid snapshot name and be given along with the corresponding fs-name.

No

path

String

Path to a directory. Shows quota report only on the specified directory.

The relevant filesystem must be mounted in the server running the query.

No

under

String

A path to a directory under a wekafs mount.

The relevant filesystem must be mounted in the server running the query.

No

over

Number

Shows only quotas over this percentage of usage

0-100

No

quick

Boolean

Do not resolve inode to a path (provides quicker result if the report contains many entries).

No

False

all

Boolean

Shows all the quotas, not just the exceeding ones.

No

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

Type

Value

Limitations

Mandatory

Default

fs-name

String

Shows the default quotas of the specified filesystem only.

A valid wekafs filesystem name.

No

All filesystems

snap-name

String

Shows the default quotas from the time of the snapshot.

Must be a valid snapshot name and be given along with the corresponding fs-name.

No

path

String

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.

No

Unsetting directory quota/default quota

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

Use the following commands to unset a directory quota:

weka fs quota unset <path>

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

weka fs quota unset-default <path>

Parameters

Name

Type

Value

Limitations

Mandatory

Default

path

String

Path to the directory to set the quota on

The relevant filesystem must be mounted when setting the quota

Yes

​

Set directory quota/default quota
List directory quotas/default quotas
Unsetting directory quota/default quota