F5 LTM/ASM Mount Issue

Hi All,

 

 

 

Apologies if this is the incorrect forum to post this however, we have had an issue recently where we experienced a failover to our standby unit, this was due to the disk space on the active unit on /var being maxed out.

 

 

We are running LTM and ASM module's on the same unit, which are;

 

6400's

 

Version 9.4.8

 

 

This is the output of the active unit, take a look at the size of /var mount

 

log df -h

 

Filesystem Size Used Avail Use% Mounted on

 

/dev/hdc5 960M 106M 806M 12% /

 

/dev/hdc7 960M 20M 892M 3% /config

 

/dev/hdc8 5.7G 4.6G 821M 85% /var

 

/dev/hdc9 960M 446M 466M 49% /usr

 

/dev/hdc2 132G 111M 125G 1% /shared

 

none 2.0G 248K 2.0G 1% /dev/shm

 

none 2.0G 1.6M 2.0G 1% /var/tmpfs

 

none - - - - /dev/mprov/tmm

 

 

This is the output of the standby unit, take a look at the size of /var mount

 

config df -h

 

Filesystem Size Used Avail Use% Mounted on

 

/dev/hdc5 5.8G 224M 5.3G 4% /

 

/dev/hdc7 5.8G 36M 5.5G 1% /config

 

/dev/hdc8 35G 4.2G 29G 13% /var

 

/dev/hdc9 5.8G 463M 5.1G 9% /usr

 

/dev/hdc1 30G 737M 28G 3% /shared

 

none 2.0G 248K 2.0G 1% /dev/shm

 

none 2.0G 1.6M 2.0G 1% /var/tmpfs

 

none - - - - /dev/mprov/tmm

 

 

We cannot explain why on the standby unit the /var mount is 35Gig, is it possible that the mount's can increase automatically and that it has grown to this size due to traffic mirroring and connection states etc?

 

 

We have had some hardware issue's on these unit historically and they have been replaced, is it possible that F5 have shipped the units back to us with different partition sizes as this is something we wouldnt have checked prior to getting the unit back into the cluster after an RMA.

 

 

 

Thanks for any help.