Mark,
Funny you should mention the RAID battery as I got this email today:
Adapter Information |
|+---------------------------------------------------------------------------+|
|| | |Adapter| BBU |BBU Learn | BBU | | ||
||ID| Adapter model |Status |Status| Cycle |charge|State |Acknowledge||
|| | | | | active | | | ||
||--+--------------------+-------+------+----------+------+------+-----------||
|| |Integrated Intel(R) | | | | | | ||
||1 |RAID Controller |OK |Not OK|- |- |Failed|No ||
|| |SROMBSASMP2 | | | | | |
However, I run your command and things look to be OK.
/opt/MegaRAID/MegaCli/MegaCli64 -adpbbucmd -getbbustatus -a0
BBU status for Adapter: 0
BatteryType: iBBU
Voltage: 4064 mV
Current: 0 mA
Temperature: 38 C
BBU Firmware Status:
Charging Status : None
Voltage : OK
Temperature : OK
Learn Cycle Requested : No
Learn Cycle Active : No
Learn Cycle Status : OK
Learn Cycle Timeout : No
I2c Errors Detected : No
Battery Pack Missing : No
Battery Replacement required : No
Remaining Capacity Low : No
Periodic Learn Required : No
Transparent Learn : No
Battery state:
GasGuageStatus:
Fully Discharged : No
Fully Charged : Yes
Discharging : Yes
Initialized : Yes
Remaining Time Alarm : No
Remaining Capacity Alarm: No
Discharge Terminated : No
Over Temperature : No
Charging Terminated : No
Over Charged : No
Relative State of Charge: 96 %
Charger System State: 49168
Charger System Ctrl: 0
Charging current: 0 mA
Absolute state of charge: 96 %
Max Error: 2 %
Exit Code: 0x00
I have a case open with support and I send then the logs to dispatch a part if needed.
Another are I would like to maybe discuss is the queue processing, rebaisng and garbage collection.
Any chance you can elaborate on each just briefly for what each does and the manual commands for each?
I did run /usr/openv/pdde/pdcr/bin/crcontrol --processqueue and it returned OK, not sure if that means it is done or what.
Lastly, something I discovered while getting the logs for support is that I have a gagillion temp vmdk files in the tmp folder. A quick search revealed that this might be an issue. https://www-secure.symantec.com/connect/forums/5220-appliance-file-system-errors-reboot-check-forced
Which you spoke on, so I am curious if you know anything more specific on the EEB for vmware. My current appliance version in 2.5.2.
At some point it might be worth investigating the fragment size you mention as well.
On the final point of one VM per data store, I will try this setting now, just to have it in place. I had it at 4...but in the long run I think the battery issue needs hashed first and then the queues, fragment size and orphaned vmdk's in the tmp folder.