Forum Discussion
F5 provisioning
Just putting my lab together and getting this message when I try adding LTM and ASM and the following error message comes up ...
01071008:3:Provisioning failed with error 1 - Disk limit exceeded. 20338MB are required to provision these modules,but only 30MB are available ...
I have 93GB of space allocated for the VM and memory of 8.5GB .
12 Replies
- Mael
Nimbostratus
We didn't have enough space to provision the ASM and AVR modules on our F5 (BIG-IP v13.1.1.4) and increasing the partition /appdata with the following command solved it:
"tmsh modify /sys disk directory /appdata new-size <new-size>" (see the KB Extending disk space on BIG-IP VE: https://support.f5.com/csp/article/K14952).
- Dario_Garrido
Noctilucent
F5 uses LVM, so "df -h" is not the command you are looking for.
Try to check the free space using
# vgsIf you need more space you should increase the size of the disk in the hypervisor and reboot the box.
Removing some installation old volumes is also a good point to free space.
https://support.f5.com/csp/article/K33265170
If you need to increase the space of an specific partition, you should resize it using this procedure
https://support.f5.com/csp/article/K14952
KR,
Dario.
- gefela
Altocumulus
I have tried resizing this by using the command: modify /sys disk logical-disk <storage name> vg-reserved <new size> but nothing is working ...
- gefela
Altocumulus
Would this article help me : https://support.f5.com/csp/article/K14843
- gefela
Altocumulus
I am using Vmware esxi 6.5
- VFB
Cirrus
Go into the settings of VMWare Player (I presume that's what you're using) and review both partitions. I currently have the first partition at 82GB and the other at 20GB. ASM requires 20GB to run.
- gefela
Altocumulus
[root@waf:Active:Standalone] config # df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg--db--vda-set.1.root 419M 77M 316M 20% /
devtmpfs 4.3G 4.0K 4.3G 1% /dev
tmpfs 4.3G 2.3M 4.3G 1% /dev/shm
tmpfs 4.3G 2.3M 4.3G 1% /run
tmpfs 4.3G 0 4.3G 0% /sys/fs/cgroup
/dev/mapper/vg--db--vda-set.1._usr 5.0G 4.0G 738M 85% /usr
/dev/mapper/vg--db--vda-dat.share 477M 100M 348M 23% /shared
none 4.3G 45M 4.3G 2% /shared/rrd.1.2
/dev/mapper/vg--db--vda-dat.appdata 31M 4.5M 25M 16% /appdata
/dev/mapper/vg--db--vda-set.1._config 469M 15M 426M 4% /config
/dev/mapper/vg--db--vda-set.1._var 922M 355M 504M 42% /var
prompt 4.0M 28K 4.0M 1% /var/prompt
none 4.3G 17M 4.3G 1% /var/tmstat
/dev/mapper/vg--db--vda-dat.log 477M 62M 386M 14% /var/log
none 4.3G 0 4.3G 0% /var/loipc
tmpfs 878M 0 878M 0% /run/user/91
tmpfs 878M 0 878M 0% /run/user/0
- VFB
Cirrus
The VM should have 2 partitions. What are the sizes of each?
- gefela
Altocumulus
I have increased to 130 GB and it is still complaining
- gefela
Altocumulus
Yes. it was 60 GB and increased it to 93 GB .. Would increasing it more make a difference
- VFB
Cirrus
Yes. I'm looking at my VM and I used 100GB and I have no issues running LTM and ASM. Try increasing it to 100GB and let me know the outcome.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com