ESXi

 View Only

  • 1.  ramdisk MAINSYS at 100%

    Posted Nov 23, 2012 09:19 AM

    Hello there

    Hope someone can help

    I'm trying to deploy a VM from template and it comes up with error below

    http://i.imgur.com/1lImA.jpg

    I have done a vdf -h on host and I can see that this is due to MAINSYS being at 100%. 32mb out of 32mb used

    I followed a few KB articles that deal with deleting 'sel' and 'sel.raw' from /var/log/ipmi/0 but issue persists. When through everything in here http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2001457 but to no luck

    Anyone has any advise or suggestions. Which partitions fall under MAINSYS to check those directories for large files on them

    Many thanks

    Petrit



  • 2.  RE: ramdisk MAINSYS at 100%

    Posted Nov 23, 2012 11:36 AM

    When you say, the issue persists, do you mean the files come back, the MAINSYS is 100% again? Or you mean you still have the problem of not being able to deploy the template?

    I assume you restarted the sfdbd service after removing the files?



  • 3.  RE: ramdisk MAINSYS at 100%

    Posted Nov 23, 2012 02:37 PM

    I mean I still can't deploy templates

    Bear in mind the files 'sel' and 'sel.raw' were very small in KBs, so issue could be somewhere else. I did restart sfcdb

    What would really help is to know what directories ammount and help with MAINSYS becoming full so that I can go to those directories and see what is taking the most space

    Any other ideas would be highly appreciated it



  • 4.  RE: ramdisk MAINSYS at 100%

    Posted Nov 23, 2012 02:52 PM

    Did you check this KB for what files are "safe" to delete when needed? http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003564

    Maybe you can find more tips on where to look for what is eating the diskspace.

    Deleting unnecessary files

    The following are a list of files that are safe to delete:

    After you have determined what is consuming disk space, delete the unnecessary files:

    1. Open a console to the ESX or ESXi host. For more information, see Unable to connect to an ESX host using Secure Shell (SSH) (1003807) or Using Tech Support Mode in ESXi 4.1 and 5.0 (1017910).

    2. Use the rm command to permanently delete files. For example:

      rm /var/log/oldlogfile

      Caution: If you delete a file, there is no way to recover it. Therefore, use caution when deleting files. If you are unsure about deleting a specific file, contact VMware Support for assistance. If a system file is removed inadvertently, it may cause damage to your ESX or ESXi host that can require a re-installation of the software.

    [edit] especially this command can give you interesting results: 

    du -h --max-depth=1 <dir>. This command lists the directories within a given filesystem that contain the largest files. By starting at the root (/) directory and finding the largest directories, you can then drill down into these directories (using cd) and execute the same command recursively until you find the files themselves which are occupying space.



  • 5.  RE: ramdisk MAINSYS at 100%

    Posted Nov 23, 2012 04:06 PM

    Right,

    Just got off the phone with the nice people at VMware Support.The nice guy was John O'Brien :smileyhappy:

    Issue is this:

    /var/log/arcconf.log had increased in size to 28mb out of 32. (It took 7 weeks to go to 28mb)  'arc' in the file stands for Adaptec Raid Controller. The solution for now is to zero out the file with echo. so, echo > /var/log/arconf.log

    The longterm solution for is that we created a crontab job which deletes the arcconf.log every week. For how to do that follow this:http://blog.armstrongconsulting.com/?cat=1 under heading "Unable to start VMs on ESXi 5.1" obviously applies to 4.1 as was my case

    John will write up a KB and follow with Adaptec on the issue, hopefully

    Thanks spravtek anyway

    Petrit



  • 6.  RE: ramdisk MAINSYS at 100%

    Posted Nov 23, 2012 04:52 PM

    Hi,

    That's a nice solution there :smileywink:

    Thanks for getting back to us with it!