understanding FS for TrueNAS

[RJ_fr33]

Hello,

why is /var/db/system not on boot-pool???

Code:

# df -h
Filesystem                                                   Size    Used   Avail Capacity  Mounted on
boot-pool/ROOT/12.0-U5.1                                      27G    1.2G     26G     4%    /
devfs                                                        1.0K    1.0K      0B   100%    /dev
tmpfs                                                         32M     10M     22M    33%    /etc
tmpfs                                                        4.0M    8.0K    4.0M     0%    /mnt
tmpfs                                                        2.6G     32M    2.6G     1%    /var
fdescfs                                                      1.0K    1.0K      0B   100%    /dev/fd
app-pool                                                      86G     24K     86G     0%    /mnt/app-pool
data-pool                                                    3.4T    244K    3.4T     0%    /mnt/data-pool
app-pool/.system                                              86G     27K     86G     0%    /var/db/system
app-pool/.system/cores                                       1.0G     24K    1.0G     0%    /var/db/system/cores
app-pool/.system/samba4                                       86G    2.5M     86G     0%    /var/db/system/samba4
app-pool/.system/syslog-21d7f87fdd8f4e01985f762f0bac7f0d      86G    1.3M     86G     0%    /var/db/system/syslog-21d7f87fdd8f4e01985f762f0bac7f0d
app-pool/.system/rrd-21d7f87fdd8f4e01985f762f0bac7f0d         86G    114M     86G     0%    /var/db/system/rrd-21d7f87fdd8f4e01985f762f0bac7f0d
app-pool/.system/configs-21d7f87fdd8f4e01985f762f0bac7f0d     86G    7.9M     86G     0%    /var/db/system/configs-21d7f87fdd8f4e01985f762f0bac7f0d
app-pool/.system/webui                                        86G     24K     86G     0%    /var/db/system/webui
app-pool/.system/services                                     86G     24K     86G     0%    /var/db/system/services

boot-pool and app-pool are on same disks on diff partitions.

app-pool:

Code:

# zpool status app-pool
  pool: app-pool
 state: ONLINE
config:

        NAME                                            STATE     READ WRITE CKSUM
        app-pool                                        ONLINE       0     0     0
          mirror-0                                      ONLINE       0     0     0
            gptid/f194e7a7-fef8-11eb-859f-00241d1d87a3  ONLINE       0     0     0
            gptid/ebc78f1d-fef8-11eb-859f-00241d1d87a3  ONLINE       0     0     0

This is my disk layout:

Code:

# gpart list |egrep 'Name:|Mediasize:|^$'
1. Name: ada0p1
   Mediasize: 2147483648 (2.0G)
2. Name: ada0p2
   Mediasize: 1998251364352 (1.8T)
1. Name: ada0
   Mediasize: 2000398934016 (1.8T)

1. Name: ada1p1
   Mediasize: 2147483648 (2.0G)
2. Name: ada1p2
   Mediasize: 1998251364352 (1.8T)
1. Name: ada1
   Mediasize: 2000398934016 (1.8T)

1. Name: ada3p1
   Mediasize: 2147483648 (2.0G)
2. Name: ada3p2
   Mediasize: 1998251368448 (1.8T)
1. Name: ada3
   Mediasize: 2000398934528 (1.8T)

1. Name: ada4s1
   Mediasize: 160040837120 (149G)
1. Name: ada4
   Mediasize: 160041885696 (149G)

1. Name: ada5p1
   Mediasize: 524288 (512K)
2. Name: ada5p2
   Mediasize: 31994150912 (30G)
3. Name: ada5p3
   Mediasize: 96040960000 (89G)
1. Name: ada5
   Mediasize: 128035676160 (119G)

1. Name: ada6p1
   Mediasize: 524288 (512K)
2. Name: ada6p2
   Mediasize: 31994150912 (30G)
3. Name: ada6p3
   Mediasize: 96040960000 (89G)
1. Name: ada6
   Mediasize: 128035676160 (119G)

1. Name: ada2p1
   Mediasize: 2147483648 (2.0G)
2. Name: ada2p2
   Mediasize: 1998251364352 (1.8T)
1. Name: ada2
   Mediasize: 2000398934016 (1.8T)

 

[ornias]

Simple: You most likely selected app-pool as the system-dataset.

 

[RJ_fr33]

i did not.
i do not remember it ever asked me that question.

 

[RJ_fr33]

how can i fix this now? i want os related stuff on boot pool.

 

[Ericloewe]

Is your boot pool redundant? The system dataset is a major pain in the ass if it's lost. Will the boot pool be able to cope with a non-insignificant volume of writes?

 

[sretalla]

Simple: You most likely selected app-pool as the system-dataset.

i did not.
i do not remember it ever asked me that question.

As soon as you create your first data pool, TrueNAS (and FreeNAS before it) ... automatically and without notice ... moves the system dataset to that new pool (and then leaves it there unless you do something).

You can select which pool should hold it from the System | System Dataset section in the GUI.

As noted by others, the selected pool should be ready to have an amount of loggiing and statistical data written to it on a constant basis, so USB boot drives are not a good target and spinning drives can be annoying with this constant activity, so an SSD pool is usually the right candidate.

 

[RJ_fr33]

As soon as you create your first data pool, TrueNAS (and FreeNAS before it) ... automatically and without notice ... moves the system dataset to that new pool (and then leaves it there unless you do something).

You can select which pool should hold it from the System | System Dataset section in the GUI.

As noted by others, the selected pool should be ready to have an amount of loggiing and statistical data written to it on a constant basis, so USB boot drives are not a good target and spinning drives can be annoying with this constant activity, so an SSD pool is usually the right candidate.

Thank you very much for the right advice. I have fixed it now.
boot-pool and app-pool are partitions of same SSD disk (mirror pair). boot is 27G. so i moved it back to boot.

have a nice day !