Forum Discussion

swo0sh_gt_13163's avatar
swo0sh_gt_13163
Icon for Altostratus rankAltostratus
Feb 11, 2014

Directory size, functionality and troubleshooting.

Hello folks,

 

Today one customer has reported an instance where he is facing an issue with configuration utility, and it was The BIG-IP System has encountered a configuration problem that may prevents the configuration utility to function properly.

 

Based on the Qkview shared by customer, I found that Appliance is running out of disk space and under the incident there was a list of directories and its file size and currently occupied size for the same. The suggested article explained to remove unnecessary files from the appliance to prevent this behavior.

 

However I found a list of directories which doesn't seem familiar to play with. Following is the list of the same.

 

/dev/md7 248M 188M 48M 80% / /dev/md8 1.7G 1.3G 296M 82% /usr 69M 69M 0 100% /tmp/eud

 

There were other directories as well, but the consumption of those directories were seeing normal. I am not aware about /MD7 /MD8 etc..

 

I need your help you understand the meaning of that directories and its role with BIG-IP. Can you please help?

 

Thank you in advance, Darshan

 

11 Replies

  • /dev/md7 248M 188M 48M 80% / /dev/md8 1.7G 1.3G 296M 82% /usr 69M 69M 0 100% /tmp/eud

     

    what is platform? is it with raid?

     

    • JG's avatar
      JG
      Icon for Cumulonimbus rankCumulonimbus
      No! That's the raid device mounted as "/"!
    • swo0sh_gt_13163's avatar
      swo0sh_gt_13163
      Icon for Altostratus rankAltostratus
      Well, the issue customer had reported was, configuration utility is not loading and keep throwing message as mentioned above in the question. And in the QKview I found that appliance is running out of disk space, so I guess that might the problem. Can you correct me if I am wrong guessing the behavior? Thanks, Darshan
  • JG's avatar
    JG
    Icon for Cumulonimbus rankCumulonimbus

    It looks like it's the root partition that is filled up. Not an uncommon problem. I am worried about this, esp. when it's time to upgrade.

     

  • Hello,

     

    The result of the command seems same as listed in the question.

     

    1. Filesystem Size Used Avail Use% Mounted on
    2. /dev/md7 248M 188M 48M 80% /
    3. /dev/md9 3.0G 137M 2.7G 5% /config
    4. /dev/md8 1.7G 1.3G 296M 82% /usr
    5. /dev/md10 3.0G 427M 2.4G 15% /var
    6. /dev/md0 30G 2.4G 26G 9% /shared
    7. /dev/md1 6.9G 185M 6.4G 3% /var/log
    8. none 4.0G 700K 4.0G 1% /dev/shm
    9. none 4.0G 17M 3.9G 1% /var/tmstat
    10. none 4.0G 1.2M 4.0G 1% /var/run
    11. prompt 4.0M 28K 4.0M 1% /var/prompt
    12. /dev/md15 12G 660M 11G 6% /var/lib/mysql
    13. /var/EUD_M-12.11.0.841.0.im 69M 69M 0 100% /tmp/eud

    Thanks, Darshan

     

    • JG's avatar
      JG
      Icon for Cumulonimbus rankCumulonimbus
      It is not obvious which fs ran out of disk space now. What are the original error messages in the logs (dmesg)?
  • Hello Jie,

     

    Sorry for the dumb question, but how can I get dmesg? I have the Qkview with me.