User guide warning... So shall we instruct collectd to save its data elsewhere?

[guermantes]

From the end of the section on "Reporting" in the 11.3 manual:
Data files are saved in /var/db/collectd/rrd/.
! Warning
Reporting data is frequently written and should not be stored on the boot pool or operating system device.

I guess it might be difficult to install Freenas correctly without sending the rrd data to the boot device in a first instance, but how would I go about selecting a new place? Is it as simple as creating a new link target for /var/db/collectd/rrd and poiting the data to my tank pool?

(If it is important enough to warrant a warning in the manual, maybe there should be a way in the GUI to select a new place for storing rrd data? I mean, Freenas is supposed to be managed through the GUI, is it not? We are often advised not to use command line-fu(/-bar)).

 

[Patrick M. Hausen]

As soon as you set up your data pool FreeNAS changes the system dataset to that. From that moment on your collected data goes there. You can verify in the menu: System -> System Dataset.

HTH
Patrick

 

[guermantes]

I am really confused now.
True, the GUI indicates that my system dataset is being stored on my pool TANK. But I thought anything that is stored on TANK would show up under /mnt/TANK/ ? Is /var/db not on the boot device? It's actually a location on my TANK pool?

 

[garm]

The mount point of a dataset can be anything. /mnt is selected by the devs, but if you set up your own system it can be anything, and the devs are free to break conformity for special cases like system dataset

 

[guermantes]

So when I SSH into the freenas, the entire filesystem I see, from / and down, is actually located on my HDDs? What's on the SSD, then?

 

[Patrick M. Hausen]

Nope, you can use the mount or df commands to see which is which:

Code:

root@freenas-pmh[~]# df
Filesystem                                             1K-blocks      Used       Avail Capacity  Mounted on
freenas-boot/ROOT/11.3-RELEASE                          30263225   1053982    29209243     3%    /
[...]
hdd/share/nextcloud                                   4849892002  14948512  4834943490     0%    /mnt/hdd/share/nextcloud
hdd/share/medien                                      5720296998 885353507  4834943490    15%    /mnt/hdd/share/medien
[...]
hdd/.system                                           4834951541      8050  4834943490     0%    /var/db/system
hdd/.system/cores                                     4834944281       790  4834943490     0%    /var/db/system/cores
hdd/.system/samba4                                    4834944025       535  4834943490     0%    /var/db/system/samba4
hdd/.system/syslog-839d4bf50898424ab2b76c72b7c93def   4834968600     25110  4834943490     0%    /var/db/system/syslog-839d4bf50898424ab2b76c72b7c93def
hdd/.system/rrd-839d4bf50898424ab2b76c72b7c93def      4835006329     62839  4834943490     0%    /var/db/system/rrd-839d4bf50898424ab2b76c72b7c93def
hdd/.system/configs-839d4bf50898424ab2b76c72b7c93def  4835038781     95290  4834943490     0%    /var/db/system/configs-839d4bf50898424ab2b76c72b7c93def
hdd/.system/webui                                     4834943618       128  4834943490     0%    /var/db/system/webui
[...]

So my Root-Filesystem is in the zpool "freenas-boot", my "share" filesystems are in the zpool "hdd" and "/var/db/system" is also in the zpool hdd.

Code:

root@freenas-pmh[~]# zpool status freenas-boot
[...]
NAME        STATE     READ WRITE CKSUM
    freenas-boot  ONLINE       0     0     0
      nvd0p2    ONLINE       0     0     0
[...]
root@freenas-pmh[~]# zpool status hdd
[...]
NAME                                            STATE     READ WRITE CKSUM
    hdd                                             ONLINE       0     0     0
      raidz2-0                                      ONLINE       0     0     0
        gptid/103e2d27-2990-11ea-80f5-ac1f6b76641c  ONLINE       0     0     0
        gptid/e505480f-29ae-11ea-80f5-ac1f6b76641c  ONLINE       0     0     0
        gptid/534f0898-2a29-11ea-ab5a-ac1f6b76641c  ONLINE       0     0     0
        gptid/59670ec1-2a4b-11ea-ab5a-ac1f6b76641c  ONLINE       0     0     0
[...]

So my zpool "freenas-boot" resides on a single NVME SSD, while my zpool "hdd" resides on 4 disks in a RAIDZ2 configuration. This doesn't tell you immediately what kind of hardware they are but you should know which disk you put into which pool.


The directory/mountpoint and the underlying storage hardware are complete de-coupled in ZFS ...


There's a script that gives you a nice summary:

Code:

root@freenas-pmh[~]# /mnt/hdd/scripts/disklist.pl
partition  label                                       zpool         device  disk                            size  type  serial            rpm
----------------------------------------------------------------------------------------------------------------------------------------------
nvd0p2     gptid/e5cf0f1d-347e-11ea-afa7-ac1f6b76641c  freenas-boot  nvd0    Samsung SSD 970 EVO Plus 250GB   250  NVME  S4EUNF1M902684R     0
ada0p2     gptid/103e2d27-2990-11ea-80f5-ac1f6b76641c  hdd           ada0    TOSHIBA HDWQ140                 4000  HDD   677FK0OUFPBE     7200
ada1p2     gptid/e505480f-29ae-11ea-80f5-ac1f6b76641c  hdd           ada1    TOSHIBA HDWQ140                 4000  HDD   6779K0VZFPBE     7200
ada2p2     gptid/534f0898-2a29-11ea-ab5a-ac1f6b76641c  hdd           ada2    TOSHIBA HDWQ140                 4000  HDD   6761K1IQFPBE     7200
ada3p2     gptid/59670ec1-2a4b-11ea-ab5a-ac1f6b76641c  hdd           ada3    TOSHIBA HDWQ140                 4000  HDD   6779K0VYFPBE     7200
ada4p1     gptid/b3378b87-3481-11ea-afa7-ac1f6b76641c  ssd           ada4    Samsung SSD 860 PRO 512GB        512  SSD   S42YNX0MA13733E     0
ada5p1     gptid/bf0126ff-347f-11ea-afa7-ac1f6b76641c  ssd           ada5    Samsung SSD 860 PRO 512GB        512  SSD   S42YNX0MA13643E     0

You can find it here: https://github.com/nephri/FreeNas-DiskList

Kind regards
Patrick

 

[guermantes]

Nice. Thanks!

 

[garm]

Try this zfs list -o name,mountpoint