On 11/1/11 11:56 AM, Tim Mooney wrote:
> If you haven't already done so, though, I highly suggest you enable the
> Linux "Magic SysRq" key on the troublesome storage node, as well as enable
> netdump(8).  Have the SysRq key guide printed out and available to your
> operators, so they can get a task list, lock list, memory state, etc.
> Might help Red Hat track down what's going on. 

I have not yet set up "Magic SysRq", but I will now.  Thank you for the idea.

-- 
Frank Swasey                    | http://www.uvm.edu/~fcs
Sr Systems Administrator        | Always remember: You are UNIQUE,
University of Vermont           |    just like everyone else.
  "I am not young enough to know everything." - Oscar Wilde (1854-1900)

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER