Forum Discussion

JG's avatar
JG
Icon for Cumulonimbus rankCumulonimbus
Jul 11, 2014

Disk space allocation

Disk space allocation varies from release to release. For example, on my v10.2.4 box, I have:

Filesystem            Size  Used Avail Use% Mounted on
    /dev/mapper/vg--db--sda-set.2.root
                          248M  130M  106M  56% /
    /dev/mapper/vg--db--sda-set.2._usr
                          1.4G  1.1G  244M  82% /usr

On a v11.2/3 box, I have:

Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/vg--db--sda-set.3.root
                      287M  191M   82M  70% /
/dev/mapper/vg--db--sda-set.3._usr
                      2.0G  1.6G  380M  81% /usr

I wonder if sizes have changed/increased in v11.4 and v11.5?

availability
deployment
management
storage
TMOS
  • Vitaliy_Savrans's avatar
    Vitaliy_Savrans
    Icon for Nacreous rankNacreous
    Jul 11, 2014

    On a 11.4.1:

    Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/vg--db--sda-set.1.root
                      380M  205M  156M  57% /
/dev/mapper/vg--db--sda-set.1._usr
                      2.2G  1.7G  422M  80% /usr
  • JG's avatar
    JG
    Icon for Cumulonimbus rankCumulonimbus
    Jul 11, 2014

    I read it somewhere that BIG-IP will create a new volume the same size as the current boot volume. If that is the case, one can only take advantage of the increased size provided by a new release by a total re-install.

     

    Can somebody please confirm / deny if this is the case?