<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, May 30, 2014 at 8:35 AM, Bryan Banister <span dir="ltr"><<a href="mailto:bbanister@jumptrading.com" target="_blank">bbanister@jumptrading.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">This sounds like a serious problem and you should open a PMR with IBM to get direct guidance.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I normally will take a GPFS trace during a problem like this from all of the nodes that are affected or directly involved in the operation.</span></p>
</div></div></blockquote><div><br></div><div>easier said than done, I've tried at least 10 times. It's almost as if the act of running the mmtrace prevents the error from occurring, we've sent internaldumps and gpfs.snap that were generated to ddn. Not having much luck in figuring out if it's been sent through to IBM yet or not.</div>
<div> </div></div></div></div>