IMO you are going to run into edge cases that nobody else ever explored - regular solutions often don't work for irregular patterns and problems. I wouldn't expect the situation where you run out of disk space in a database directory but not on the redo log and/or master tablespace to be well tested. If you want something that will "just work" for resource isolation, your best option is probably to have smaller VMs, one for each user.
On Wed, 13 Aug 2025 at 14:25, sacawulu via discuss <discuss@lists.mariadb.org> wrote: > > Hi Karl, > > Thanks, yes: multi-tenancy would do what I am looking for. > > I am now testing with xfs quota, one single LVM for /var/lib/mysql, > mounted wth prjquota, with limits assigned to the DB directories below: > > Filling it like this: > > > MariaDB [db1]> CALL fill_db1(); > > ERROR 1114 (HY000): The table 'fill_table' is full > > MariaDB [db1]> exit > > and the result being: > > > [root@ruby mysql]# xfs_quota -x -c 'report -p' /var/lib/mysql > > Project quota on /var/lib/mysql (/dev/mapper/mysql-mysql) > > Blocks > > Project ID Used Soft Hard Warn/Grace > > ---------- -------------------------------------------------- > > #0 127712 0 0 00 [--------] > > db1 9220 8192 10240 00 [7 days] > > db2 0 18432 20480 00 [--------] > > db3 0 28672 30720 00 [--------] > > db4 4 38912 40960 00 [--------] > > Any objections to that approach? > > I think (also @Gordan) that this would address the concerns that were > risen, right..? > > _______________________________________________ > discuss mailing list -- discuss@lists.mariadb.org > To unsubscribe send an email to discuss-le...@lists.mariadb.org -- Gordan Bobic Database Specialist, Shattered Silicon Ltd. https://shatteredsilicon.net Follow us: LinkedIn: https://www.linkedin.com/company/shatteredsilicon X: https://x.com/ssiliconbg _______________________________________________ discuss mailing list -- discuss@lists.mariadb.org To unsubscribe send an email to discuss-le...@lists.mariadb.org
