In Ubuntu Server and other modern Linux distributions, systemd-quotacheck.service is an early-boot systemd component responsible for enforcing and verifying disk quotas during the startup sequence. It acts as a wrapper around the traditional quotacheck command-line utility, scanning file systems defined in /etc/fstab (with quota options enabled) to ensure that block and inode usage aligns with established limits before mounting them read-write. While useful in multi-tenant shared hosting environments where user disk space must be strictly policed, this service introduces unnecessary boot latency and complexity in strict, single-purpose infrastructure (such as dedicated database servers, stateless microservice nodes, or immutable Kubernetes workers). If the infrastructure relies entirely on volume-level sizing (like AWS EBS or Ceph) rather than legacy POSIX user/group quotas, allowing this service to trigger filesystem scans at boot is an operational inefficiency.
This guide explains how to completely disable the systemd-quotacheck service in Ubuntu Server, ensuring absolute suppression of automated legacy quota verification during the boot sequence.
Stop and Mask the systemd-quotacheck Service
Because this service executes extremely early in the boot process (prior to the local-fs.target being reached), simply issuing a ‘disable’ command is insufficient. We must explicitly mask the unit file to guarantee the systemd init process is physically prevented from executing it.
- Log into your Ubuntu Server via SSH using an account with
sudoprivileges. - Check if the service is currently active or loaded:
sudo systemctl status systemd-quotacheck.service - Disable the service to remove it from the systemd boot schedule targets:
sudo systemctl disable systemd-quotacheck.service - For absolute certainty, explicitly mask the service. This symlinks the unit file to
/dev/null, creating a hard cryptographic block against it being invoked by systemd under any circumstances:sudo systemctl mask systemd-quotacheck.service
Verify the Service Lockdown
By masking systemd-quotacheck.service, you guarantee that systemd will completely bypass legacy quotacheck operations during the boot sequence, immediately mounting filesystems without attempting to verify user/group block usage, thereby accelerating the boot time of dedicated infrastructure nodes.
To verify the lockdown is successful, attempt to start the service manually:
sudo systemctl start systemd-quotacheck.serviceSystemd will return a fatal error stating that the unit is masked (e.g., Failed to start systemd-quotacheck.service: Unit systemd-quotacheck.service is masked). You have successfully neutralized the automated quota verification mechanism, streamlining your server’s early-boot environment and ensuring compliance with modern, volume-based infrastructure provisioning requirements.