Changes between Version 206 and Version 207 of Processing

Timestamp:

Feb 22, 2016, 1:03:21 PM (10 years ago)

Author:

Mark Huber

Comment:

--

Processing

@@ -609 +609 @@
 
 {{{
-neb-host ipp016 repair
-}}}
+neb-host ipp016 repair --note 'problem desc'
+}}}
+
+'''be sure to always leave a note'''
 
 This leaves the machine accessible, but no new data can be allocated to it. See table below for a guide to the other nebulous states
@@ -621 +623 @@
 Running {{{neb-host}}} with no arguments gives you a summary of the above for all hosts.
 
+
+
+
 === Non-Troublesome Hosts ===
 The same commands can be used for non-troublesome hosts.
@@ -632 +637 @@
 (SC TODO) {{{controller status}}} shows something looking like an addresse (e.g., 0.0.0.7d) which is different for each connection. It seems it's not possible to remove a particular connection. Am I right?
 
+== Raid BBU and Nodes with Targeted Data ==
+
+Many times a node becomes problematic when the raid BBU goes offline and WriteThrough (rather than WriteBuffer) mode is activated -- definitely happens for a data targeted node, but can also happen for an untargeted node if there are very few targeted nodes with free space. The node should be checked and if BBU needs attention then notify the ipp-dev list for the appropriate person to do so. To check the BBU status, there are two possible commands depending on the node but try the command as given on a machine that doesn't support it the it should be fine (requires sudo and be careful with these commands not to mistype or truncate) -- 
+
+ * ipp083 (add more to list here as go)
+{{{
+--> MegaCli64 -AdpBbuCmd -aAll
+
+Battery State: Optimal 
+
+... lots of other details ...
+
+
+--> MegaCli64 -LDInfo -Lall -aALL
+
+Default Cache Policy: WriteBack, ReadAheadNone, Cached, No Write Cache if Bad BBU
+Current Cache Policy: WriteBack, ReadAheadNone, Cached, No Write Cache if Bad BBU
+
+
+}}}
+  * want '''WriteBack''' for Current Cache Policy not WriteThrough
+
+ * ipp096 (add more to list here as go)
+{{{
+--> tw_cli /c0 show
+
+Unit  UnitType  Status         %RCmpl  %V/I/M  Stripe  Size(GB)  Cache  AVrfy
+------------------------------------------------------------------------------
+u0    RAID-6    OK             -       -       256K    81956.2   RiW    ON    
+
+... other raid info ...
+
+Name  OnlineState  BBUReady  Status    Volt     Temp     Hours  LastCapTest
+---------------------------------------------------------------------------
+bbu   On           Yes       OK        OK       OK       85     18-Jul-2015  
+}}}
+  * want to see Cache '''RiW'''
+
+IF the problem node is a data targeted node and enough data nodes (and most of target data nodes) are available, the problem data node may still be able to take random data, but needs to be removed from the targeted set and pantasks restarted (typically the following day if BBU or full node issues not addressed) -- for the ipp-20141024 tag
+{{{
+~ipp/psconfig/ipp-20141024.lin64/share/pantasks/modules/ipphosts.mhpcc.config
+}}}
+
+
 == Corrupted data before the current stage ==
+
 The ~ipp/src/ipp-<version>/tools directory contains a bunch of tools that can be used to fix weird problems.
 For instance, I had a repeating entry telling that warp failed because of a corrupted cam generated file.
@@ -789 +839 @@
 
 The IPP svn/wiki is on ipp002 and has also been known to crash, once rebooted the svn and wiki should be available again.
+
+
 = Who to contact =