Whan you are creating the first ELM pool, system create ELM database on that pool. Default size of that database is exactly 500GB and there is no possibility to change this value.
Checking of ELM statistics: Receiver\ELM Properties, Receiver\ELM Management, View Statistics
Looks like you setup the "data" i.e. logs files and management Database to share the same CIFS location which is OK. We mirror the ManagementDB locally and on our NFS share.
So what you probably are seeing is that the elm data files are split into 2GB chunks: ( an example of our NFS listing )
-rw-r--r-- 1 root root 2147152476 Dec 23 03:51 sh_2_sr_56.elm
-rw-r--r-- 1 root root 2147246621 Feb 28 00:48 sh_2_sr_2.elm
-rw-r--r-- 1 root root 2147237228 Mar 4 15:08 sh_2_sr_3.elm
-rw-r--r-- 1 root root 2147435899 Mar 8 17:42 sh_2_sr_1.elm
-rw-r--r-- 1 root root 2147017266 Mar 12 19:21 sh_2_sr_4.elm
-rw-r--r-- 1 root root 2147272307 Mar 16 21:33 sh_2_sr_5.elm
If you were to log into the elm via putty/ssh and cat /etc/NitroGuard/alloc.conf and /etc/NitroGuard/storage.conf along with a df command it makes more sense.
example stroage.conf using NFS you could in a putty/ssh session on the ELM run "ls -latr" on the "mount" value in your storge.conf file.