Friday, May 04, 2012 7:21 PM
Issue: "Drives are at risk of running out of free space" error appears to be spurious, but want to confirm.
Environment: Production system, VMWare virtual machine, W2K8 R2 OS. SharePoint and SQL on separate VMs. Sharepoint VM has 8 GB of memory. SharePoint VM configured with three drives: C for OS (37 out of 59.8GB is free); D for pagefile (46.9 out of 54.0 GB is free); and E for application data (30.5 out of 39.9 GB is free).
Virtual memory configured as follows: C: None; D: 56,267 MB (system managed size); E: None
Health Analyzer is suggesting the following error:
Title: Drives are at risk of running out of free space.
Severity: 2 - Warning
Explanation: Available drive space is less than five times the value of physical memory. This is dangerous because it does not provide enough room for a full memory dump with continued operation. It also could cause problems with the Virtual Memory swap file: System (PB-PROD-APP-1 - C:\), App (PB-PROD-APP-1 - E:\).
Remedy: Examine the failing servers and delete old logs or free space on the drives. For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=142688".
Failing Servers: PB-PROD-APP-1
Failing Services: SPTimerService (SPTimerV4)
- Free space on the actual drive on which virtual memory is configured (i.e., D) appears to be within SharePoint guidelines. I.e., there is 46.9 GB of free space which is greater than 5 times the 8 GB of memory.
- Free space on both C and E (neither of which are configured to host virtual memory) is less than 40GB (i.e., 5 times 8 GB of memory), but that shouldn't matter.
- The actual Central Administration error message specifies that the problematic drives are C and E ... which have no virtual memory configured for them???
Am I correct is my observation? Is this a spurious error? Is there (or will there be) at MS patch to address this? If my observations are incorrect, how should I be interpreting the error?
Friday, May 04, 2012 7:49 PM
This is more of a recommendation than an warning/error(if less than 2xRAM). I see this all the time, the important thing is that you are aware of your environment. To make a full memory dump and need 4x RAM of free space is only needed if you are ever going to use the memorydump for t-shooting or debugging.
I would say, if you feel ok with your environment and the configuration you have, RAM and disk space, then ignore this 'warning'. I doubt that it will be 'fixed' now after 2 years.
Read up on them all here:
SharePoint Health Analyzer rules reference (SharePoint Server 2010)
Monday, May 14, 2012 1:59 PM
Just to be clear:
- Yes, there is a bug in the health analyzer algorithm;
- However, as long as I've verified that virtual memory is configured to be 5x RAM then the 'warning' can be ignored as spurious.
If these statements are true, then it would be great if someone from MS could explore whether the health analyzer algorithm in SharePoint 15 could be a bit more sophisticated.