Starting in LMI 6.2.1 the /var/ directory is now a separate mountpoint and is configured as a bind mount on /tmp. In addition, the llllv_tmp logical volume has been renamed to lllv_var. As a result of these changes the df output will look like this:

Logapp root:/loglogic 0$ df -h
Filesystem            Size  Used Avail Use% Mounted on
devtmpfs              7.9G  192K  7.9G   1% /dev
tmpfs                 7.9G     0  7.9G   0% /dev/shm
/dev/sda1             5.8G  1.5G  4.1G  27% /
/dev/sda2             5.8G   12M  5.5G   1% /failsafe
/dev/mapper/llvg-lllv_var
                      4.8G   81M  4.5G   2% /var
/dev/mapper/llvg-lllv_db
                      466G  3.3G  462G   1% /loglogic
/dev/mapper/llvg-lllv_var
                      4.8G   81M  4.5G   2% /tmp
/dev/mapper/llvg-lllv_var
                      4.8G   81M  4.5G   2% /tmp
none                  802M  4.0K  802M   1% /loglogic/data/dbi

Although lllv_var logical volume is listed 3 times this is normal and is a result of it being mounted on /var and the bind mount to /tmp. A known Linux issue causes that bind mount to be listed twice so the output is to be expected based on all that information.

Note that the size of /tmp is 4.8GB on a new installation but is about 1GB in size on upgraded systems.

The logical volumes and mountpoints have changed in LMI 6.2.1. This article explains how these changes affect the output of the df command.