Fusequota

Fusequota is a user-space filesystem built on FUSE (Filesystem in Userspace) that enforces per-server disk limits. It works on top of whatever filesystem your server volumes already live on - ext4, XFS, network mounts, and others - without requiring native filesystem support for quotas.

How It Works

Wings spawns a dedicated FUSE daemon process per server. The daemon intercepts all filesystem calls and tracks cumulative disk usage, rejecting writes that would exceed the configured server disk limit.

Strengths

• Works on any filesystem type - no migration required
• Existing server data does not need to be moved or reformatted
• Compatible with standard server volume layouts

Trade-offs

Fusequota works on any filesystem, which makes it the only option on hosts that cannot use a native quota system. On hosts where Btrfs, ZFS, or XFS project quotas are available, a native limiter is the better choice for production workloads.

• Performance - FUSE adds user-space overhead to every filesystem operation. I/O-heavy games (Minecraft chunk generation, database-heavy games) will feel this most.
• Stability - after a crash or unexpected restart, a FUSE mount can be left behind and needs manual cleanup before the server directory is accessible again.
• Game compatibility - some games and mods rely on filesystem behavior that FUSE handles differently.
• Docker - with Docker-based Wings, restart cycles can leave orphaned FUSE mounts that require manual cleanup; a native limiter is a better fit here.

When to Use

Fusequota is the right choice when your host filesystem has no Btrfs, ZFS, or XFS project quota support and you still need disk limit enforcement (e.g. in a shared or low-trust environment). On hosts with native quota support, prefer the corresponding limiter.

Configuration

In /etc/pterodactyl/config.yml, set:

system:
  disk_limiter_mode: fuse_quota

Restart Wings after changing this value.