LEIL-REPQUOTA(1)

📦 version 5.12.0, in nixpkgs unstable

💅 LEIL-REPQUOTA — the leil repquota / leil setquota glow-up ✨

okay so bestie, this is the LEIL-REPQUOTA(1) page and it's genuinely so useful — it's all about peeking at quotas and setting them. no cap. let's get into it 🫶

✨ NAME ✨

leil-repquota, leil-setquota — these two icons literally retrieve and set quotas for the users and groups you point at 💖

🌸 SYNOPSIS 🌸

here's the whole vibe check, exactly as written:

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

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

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

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

leil 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' uid UID 👑
  • -g 'GID' — the quota for the group rockin' gid GID 💜
  • -a — quota for all the users and groups, everybody, the whole group chat 🫶
  • -d — quota for a directory 🍓

🦋 DESCRIPTION 🦋

so the quota mechanism is literally there to limit inode usage and space usage for users and groups. once the hard limit for inodes or for space gets hit, no new files can be created for that specified user (or group) — unless the quota gets raised or some data gets deleted. and 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, bestie: you can set SESFLAG_ALLCANCHANGEQUOTA in leil-exports.cfg. 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 plus 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'

‘' means the soft limit was exceeded or the hard limit was reached. - means otherwise. the first ‘' or - is for the bytes limit, and the second one is for inodes 👀

setquota sets quotas for a user or a group on LeilFS. and ngl, these quotas are not strict — it's possible to exceed hard limits a little bit, mostly by appending data to existing files, but only up to a certain level (new chunks cannot be created). so like, don't get too comfy 😭

⚠️ fr fr remember: hard limit on inodes or space ⇒ no new files for that user/group until the quota is raised or data is deleted. and size hard limit ⇒ no extending existing files with new chunks.

🔥 REPORTING BUGS 🔥

found a bug? don't suffer in silence bestie — report it to the GitHub repository https://github.com/leil-io/leilfs as an issue 🐛

Copyright 2008-2009 Gemius SA

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

Copyright 2023-2024 Leil Storage OÜ

LeilFS 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. ✨

LeilFS 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 LeilFS. if not, see http://www.gnu.org/licenses/. 🎀

🌟 SEE ALSO 🌟

leil(1) — go read it, it's giving main character energy 💅

okay that's the whole page, bestie — official vibes: source LEIL-REPQUOTA(1), dated 1980-01-01. slay, you're now a quota expert 🧚💖

📦 where this page comes from