SAUNAFS-REPQUOTA(1)

🌸 SAUNAFS-REPQUOTA(1) — bestie edition 🌸

okay so hi!! welcome to the saunafs-repquota / saunafs-setquota page, section 1 of the manual, and honestly? it's giving quota queen. two tools, one page, zero gatekeeping. let's go 💅

---

✨ NAME ✨

saunafs-repquota, saunafs-setquota — these two cuties retrieve and set quotas for the users and groups you specify 🫶

---

📖 SYNOPSIS 📖

lowkey just read the receipts, bestie:

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

saunafs repquota [-nhH] -a 'MOUNTPOINT-ROOT-PATH'

saunafs repquota [-nhH] -d 'DIRECTORY-PATH'

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

saunafs setquota -d 'SOFT-LIMIT-SIZE' 'HARD-LIMIT-SIZE'
              'SOFT-LIMIT-INODES' 'HARD-LIMIT-INODES' 'DIRECTORY-PATH'

---

🎀 OPTIONS 🎀

• -u UID — the quota for the user with uid UID. your user, your rules ✨
• -g GID — the quota for the group with gid GID. squad limits, periodt 👑
• -a — the quota for all users and groups. everybody gets a number 🫶
• -d — the quota for a directory. it's giving location-based 🦋

ngl the synopsis also waves -nhH around for repquota, and that's exactly how it's written up top — no extra explanation here, so I'm not gonna invent one 💀

---

💖 DESCRIPTION 💖

so the quota mechanism is how you put a ceiling on inodes usage and space usage for users and groups. iconic. ✨

once the hard limit for inodes or space is reached, no new files can be created for that specified user (or group) — not until the quota gets raised or somebody deletes some data. 😭 also, if the hard limit for size is hit, the user cannot extend existing files by adding new chunks to them. no new chunks, no new drama. 🌸

in general, quotas can be set only by a superuser, but there's a workaround available — you can set SESFLAG_ALLCANCHANGEQUOTA in the sfsexports.cfg file. main character energy 🔥

and a user can only retrieve a quota of his own (and of his primary group). know your lane, bestie 💅

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 exact format:

# 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 was exceeded or the hard limit was reached. - indicates otherwise. the first ‘`' or - corresponds to bytes limit, while the second one to inodes. two little symbols, so much lore 🦋

setquota sets quotas for a user or a group on SaunaFS. and heads up — 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). it's a soft little overshoot, not a whole rebellion 🙈

---

🐛 REPORTING BUGS 🐛

found a bug? report it to the GitHub repository https://github.com/leil-io/saunafs as an issue. do it for the girls 💜

---

⭐ COPYRIGHT ⭐

Copyright 2008-2009 Gemius SA

Copyright 2013-2019 Skytechnology sp. z o.o.

Copyright 2023-2024 Leil Storage OÜ

SaunaFS 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.

SaunaFS 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 SaunaFS. If not, see http://www.gnu.org/licenses/.

---

🌈 SEE ALSO 🌈

• saunafs(1)

---

and that's the whole page, bestie — no cap. this was SAUNAFS-REPQUOTA(1), dated 2026-07-29, and yes the version string at the bottom is literally just the page name again because that's how manpages do 😭 slay, go set some quotas, ily 🎀💖✨