LIZARDFS-REPQUOTA(1)

💖 LIZARDFS-REPQUOTA(1) 💖

ok so bestie, welcome to lizardfs-repquota and lizardfs-setquota — the quota duo. no cap, these two are literally the vibe check for how much space and how many inodes your users and groups are allowed to eat. 🍓

---

✨ NAME ✨

lizardfs-repquota, lizardfs-setquota — retrieves and sets quotas for specified users and groups 🫶

---

🌸 SYNOPSIS 🌸

lizardfs repquota [-nhH] (-u UID | -g GID)+ MOUNTPOINT-ROOT-PATH

lizardfs repquota [-nhH] -a MOUNTPOINT-ROOT-PATH

lizardfs repquota [-nhH] -d DIRECTORY-PATH

lizardfs setquota (-u UID | -g GID) SOFT-LIMIT-SIZE HARD-LIMIT-SIZE
              SOFT-LIMIT-INODES HARD-LIMIT-INODES MOUNTPOINT-ROOT-PATH

lizardfs setquota -d SOFT-LIMIT-SIZE HARD-LIMIT-SIZE
              SOFT-LIMIT-INODES HARD-LIMIT-INODES DIRECTORY-PATH

---

💅 OPTIONS 💅

• -u UID — the quota for the user rockin' that uid UID. 👑
• -g GID — the quota for the group with gid GID. 🫂
• -a — quota for all the users and groups, the whole squad. 🌈
• -d — quota for a directory. 📁

---

🦋 DESCRIPTION 🦋

So the quota mechanism is literally there to limit inodes usage and space usage for users and groups. the way that it works is: once the hard limit for inodes or space is reached, no new files can be created for that specified user (or group) — and that stays true for as long as the quota isn't raised or some data gets deleted. 💀 also, if the hard limit for size is reached, the user cannot extend existing files by adding new chunks to them. periodt.

in general, quotas can only be set by a superuser, but there's a workaround available — you can set SESFLAG_ALLCANCHANGEQUOTA in the mfsexports.cfg file. 🙈 and a user can only retrieve a quota of their own (and of their primary group). iykyk.

repquota prints a summary of the limits that were set and the inode/space usage for the specified user/group (or all of them), in this format, exactly:

# User/Group ID/Inode; Bytes: current usage, soft limit, hard limit; Inodes: current usage, soft limit, hard limit;
User/Group/Inode ID (+/-)(+/-) USED-BYTES SOFT-LIMIT-BYTES HARD-LIMIT-BYTES USED-INODES SOFT-LIMIT-INODES HARD-LIMIT-INODES

+ indicates that the soft limit was exceeded or the hard limit was reached. - indicates otherwise. the first + or - corresponds to the bytes limit, while the second one is for inodes. 🔥

setquota sets quotas for a user or a group on LizardFS. lowkey important: the quotas are not strict, i.e. it is possible to exceed hard limits a bit — mostly by appending data to existing files — but only to a certain level (new chunks cannot be created). ✨

bestie, that "not strict" thing is a real caveat, not a cute quirk. plan accordingly. 💖

---

🎀 COPYRIGHT 🎀

Copyright 2008-2009 Gemius SA, 2013-2016 Skytechnology sp. z o.o.

LizardFS is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, version 3.

LizardFS is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with LizardFS. If not, see http://www.gnu.org/licenses/.

---

👑 SEE ALSO 👑

• lizardfs(1)

---

k that's the whole page bestie, slay. this was LIZARDFS-REPQUOTA(1) from the 07/24/2025 era, and you're all caught up. go set some quotas, main character energy only. 💜🦋🌸