Skip to content

Limits

Files quotas, throughput and metadata limits per file system, and what happens when a file system reaches them.

Updated View as Markdown

Quotas

Files’ service quotas are all adjustable. Your organization’s current values are in the console’s Service quotas page, where you can request an increase up to the maximum.

Quota ID Default Maximum
File systems per organization files.fileSystemsPerOrganization 10 1,000
Mount targets per file system files.mountTargetsPerFileSystem 16 64
Access points per file system files.accessPointsPerFileSystem 100 1,000
Stored GiB per organization files.bytesPerOrganization 1,024 GiB 102,400 GiB
Throughput per file system files.throughputMBpsPerFileSystem 100 MB/s 10,000 MB/s
Metadata operations per file system files.metadataOpsPerFileSystem 2,000 per second 100,000 per second

A create over a count quota is refused with 409 quota_exceeded, naming the quota.

Over a limit

  • Throughput and metadata operations. A file system’s limits show its values. Over them, clients are slowed, never refused: reads, writes and lookups take longer, and nothing fails.
  • Stored bytes. File systems’ sizes are measured about once an hour. When a measurement shows the organization’s file systems at the quota or over it, they stop growing: within seconds, writes that need more space fail with EDQUOT (“Disk quota exceeded”). Reads and deletes keep working, and nothing is deleted. Free space or raise the quota, and writes work again after the next measurement.

Other limits

Limit Value
Mount targets per subnet, per file system 1
Allowed source CIDRs per mount target 1 to 50, IPv4
Access point root path 255 characters
Name 1 to 100 characters
Description 500 characters
Connections per client (nconnect) 16
Navigation

Type to search…

↑↓ navigate↵ selectEsc close