For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

lostinberlin_11's avatar
lostinberlin_11
Icon for Nimbostratus rankNimbostratus
Jun 23, 2015

BIGI LTM VE qcow2 image - Shared directory too small for upgrade

We are in the process of migrating our servers from BIGIP 11.3 to 11.6.

I am trying a test upgrade with the BIGIP-11.3.0.39.0.qcow2 image.

However, the 

/shared
directory is too small to hold the 11.6 image (over 1GB) for the upgrade procedure. 

[root@localhost:Active:Standalone] config  df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/vg--db--hda-set.1.root
                      380M  187M  174M  52% /
/dev/mapper/vg--db--hda-set.1._config
                      477M   15M  438M   4% /config
/dev/mapper/vg--db--hda-set.1._usr
                      2.2G  1.4G  746M  65% /usr
/dev/mapper/vg--db--hda-set.1._var
                      477M  160M  293M  36% /var
/dev/mapper/vg--db--hda-dat.share.1
                      485M   37M  423M   9% /shared
/dev/mapper/vg--db--hda-dat.log.1
                      485M   28M  432M   6% /var/log
none                  502M  708K  501M   1% /dev/shm
none                  502M  4.9M  497M   1% /var/tmstat
none                  502M  1.3M  501M   1% /var/run
prompt                4.0M   28K  4.0M   1% /var/prompt

Can anyone tell me how to increase the 

/shared
directory?

From 11.5 the 

tmsh modify sys disk directory
command is available, but I haven't found anything for 11.3.

Thanks for any help you can offer.

Steve

deployment
storage
TMOS
TMSH
virtualization

1 Reply

  • lostinberlin_11's avatar
    lostinberlin_11
    Icon for Nimbostratus rankNimbostratus
    Jun 25, 2015

    I managed to work this out and am posting the solution to help anyone who has the same problem.

    Basically, you need to:

    • boot into the BigIP MOS (Maintenance Operating System)
    • extend and resize the logical shared partition
    • reboot

    The steps are as follows:

    • boot into the BigIP MOS (Maintenance Operating System)

      • boot into the BigIP as normal
      • use the 
        grub_open
        command the get the grub file to modify
      • edit the file, changing default to '1' instead of '0'
      • use the 
        grub_close
        command to save the modified file.
      • reboot. This time the VM should go into 'MOS' mode without mounting any of the file systems.

    • extend and resize the logical shared partition

      • use 
        lvscan
        to list the available partitions
      • use 
        lvextend
        to extend the partition in question (Reference: http://tldp.org/HOWTO/LVM-HOWTO/extendlv.html)
      • use 
        resize4fs
        to resize the enlarged partition.
      • reboot. The default is reset automatically and the VM reboots into normal mode.

    Now you should see that the mount has been resized.

    Hope it helps someone.

    Cheers, Steve