Quota exceeded on dataset <...>/.system/cores

TrueNAS General
,
1

I remember after updating to one of the later versions I got flooded with alerts (a few emails an hour):

Quota exceeded on dataset <…>/.system/cores. Used 97.86% (1002.13 MiB of 1 GiB)

So I reverted back to the version I was using and waited for another update and alerts disappeared. I was using 24.04 and then upgraded to 24.10.0 and there were no such alerts, but after updating to 24.10.1 these alerts came back and I’m getting them multiple times a week.

It seems I can’t find anything on the topic :confused:

Anything I should look into? Should I change some settings?

1 Like
2

Delete the cores

3

So one of the errors is:

Quota exceeded on dataset Data/.system/cores

How do I delete cores? There’s no such folder .system inside Data :confused: Do I need to enable something to see it?

$ cd /mnt/Data/.system
cd: no such file or directory: /mnt/Data/.system

Update:
Found it with

$ /usr/sbin/zfs list

NAME                                                                       USED  AVAIL  REFER  MOUNTPOINT
Data/.system                                                              2.09G  7.20T  1.47G  legacy
Data/.system/configs-ae32c386e13840b2bf9c0083275e7941                     16.0M  7.20T  16.0M  legacy
Data/.system/cores                                                         127M   897M   127M  legacy
Data/.system/netdata-ae32c386e13840b2bf9c0083275e7941                      483M  7.20T   483M  legacy
Data/.system/nfs                                                           149K  7.20T   149K  legacy
Data/.system/samba4                                                       2.51M  7.20T   687K  legacy

Should I delete the whole .system maybe? My other data pool doesn’t have it at all and mountpoint says legacy :thinking:

4

I wouldn’t advice removing the whole system dataset unless you really had to.

I believe the cores dataset is mounted here:
/var/db/system/cores

1 Like
5

Would it be safe to use this?

$ /usr/sbin/zfs destroy Data/.system/cores
6

No. Its a folder not a dataset

1 Like
7

Aren’t those core dumps? How often do core files get created? I’ve only ever had one core file in my entire time using FreeNAS and TrueNAS Core.

Maybe it’s apt for a bug report?

8

How?

I can’t cd to it as .system doesn’t exist on the datasat

9

Because there is no folder named “.system”. That’s the hidden dataset’s name. Datasets can be mounted to any path.

The cores are found under /var/db/system/cores/

10

There’s none at presnt

TRUENAS-SCALE% pwd
/var/db/system/cores
TRUENAS-SCALE% sudo ls -la
total 33
drwxr-xr-x 2 root root 2 May 20 01:34 .
drwxr-xr-x 9 root root 9 Nov  3  2024 ..
TRUENAS-SCALE%

I managed to see some brieftly before it disappeared earlier due to perodic job


TRUENAS-SCALE% cd /var/db/system/cores/
TRUENAS-SCALE% ls -la
total 384338
drwxr-xr-x 2 root root         3 May 20 01:09 .
drwxr-xr-x 9 root root         9 Nov  3  2024 ..
-rw-r----- 1 root root 393219960 May 20 01:09 core.python.0.e95a7a4259574f679dc5f1e0831d4832.4066500.1747699778000000.zst
TRUENAS-SCALE% ls -la
total 187422
drwxr-xr-x 2 root root         3 May 20 01:10 .
drwxr-xr-x 9 root root         9 Nov  3  2024 ..
-rw-r----- 1 root root 191726646 May 20 01:10 core.python.0.e95a7a4259574f679dc5f1e0831d4832.4067678.1747699804000000.zst
TRUENAS-SCALE% ls -la

is there any way to increase the quota? so I don’t keep getting the alerts - it was fixed but having it set at 1GiB seems to small

11

Generally it’s fine. Corefiles are very compressible and you shouldn’t be generating them. Usually their presence in a stable release indicates:

  1. broken custom application
  2. failing boot device
  3. unexpected OS changes