Reporting database size (1.4 GB) is larger than 1 GiB. Any way to trim down the database?

jjstecchino

Contributor
Joined
May 29, 2011
Messages
136
I am getting the alert on Truenas Scale Nightly: "Reporting database size (1.4 GB) is larger than 1 GiB".
Is there any way to trim the database in the GUI or shell?

Thanks
 

rmont

Dabbler
Joined
Jun 18, 2020
Messages
42
I'm getting the same error (on 22.02 RC2). Did you find a way to fix it?
 

Toffi-Fee

Cadet
Joined
Oct 25, 2021
Messages
1
Same. In this thread @morganL says that this warning doesn’t necessarily need to be a problem.
But what is the purpose of this message then and how do I know when it starts to be a problem?
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,702
I never saw the reason explained, but some of the system dataset (children) have a 1G quota set on them...

you can find it by using zfs get quota and looking for the ones with 1G (could be a very long list).

If your pool hosting the dataset has ample space, you can just change that by using zfs set quota=2G pool/path/to/dataset or whatever
 

mattyv316

Dabbler
Joined
Sep 13, 2021
Messages
27
I never saw the reason explained, but some of the system dataset (children) have a 1G quota set on them...

you can find it by using zfs get quota and looking for the ones with 1G (could be a very long list).

If your pool hosting the dataset has ample space, you can just change that by using zfs set quota=2G pool/path/to/dataset or whatever
I am seeing this same issue on TrueNAS-SCALE-22.02-RC.2. I found a 1G quota that I updated to 4G, but this did not help. My email box is still getting these notifications constantly. I even changed the alert frequency to daily on the following alerts under storage:
Critical Quota Exceeded on Dataset
Quota Exceeded on Dataset

None of these changes seemed to have any affect. Has anyone had any luck resolving this?
 

atomcycom

Cadet
Joined
Mar 6, 2022
Messages
1
Hi, I have encounter this error after I setup a VM in my Truenas Scale. Seems like this error is not fixed in the version SCALE 22.02.0.
Since then, I've been getting this alert in hourly.
Anyone can guide me on fixing this?
 

binarybcc

Dabbler
Joined
Mar 16, 2020
Messages
20
Top