/home
can have a quota of 1TiB, and each user directory under it can have a quota of 10GiB, while there are 200 users.EXDEV
in such a case, which is usually converted by the operating system to copy&delete but is OS-dependent.writecache
mount-mode, similarly to other POSIX solutions, getting above the quota might not sync all the cache writes to the backend servers. Use sync
, syncfs
, or fsync
to commit the cached changes to the system (or fail due to exceeding the quota).df
utilitydf
utility will consider the hard quota as the total capacity of the directory and provide the use%
relative to the quota. This can help users understand their usage and how close they are to the hard quota.df
utility behavior with quotas is currently global to the Weka system. weka fs quota set
/ weka fs quota set-default
weka fs quota set <path> [--soft soft] [--hard hard] [--grace grace] [--owner owner]
weka fs quota set-default <path> [--soft soft] [--hard hard] [--grace grace] [--owner owner]
path
soft
grace
period is over.1GB
, 1TB
, 1GiB
, 1TiB
, unlimited
unlimited
hard
1GB
, 1TB
, 1GiB
, 1TiB
, unlimited
unlimited
grace
1d
, 1w
, unlimited
unlimited
owner
soft
quota limit without setting a grace
period.weka fs quota list
/ weka fs quota list-default
weka fs quota list [fs-name] [--snap-name snap-name] [--path path] [--under under] [--over over] [--quick] [--all]
fs-name
snap-name
fs-name.
path
under
over
quick
all
weka fs quota list-default [fs-name] [--snap-name snap-name] [--path path]
fs-name
snap-name
fs-name.
path
weka fs quota unset
/ weka fs quota unset-default
weka fs quota unset <path>
weka fs quota unset-default <path>
path