[gpfsug-discuss] Potential problems - leaving trace enabled in over-write mode?
Oesterlin, Robert
Robert.Oesterlin at nuance.com
Tue Mar 7 21:25:05 GMT 2017
mmfsd crash - IBM says, “we need a trace to debug the issue”.
Sigh
Bob Oesterlin
Sr Principal Storage Engineer, Nuance
From: <gpfsug-discuss-bounces at spectrumscale.org> on behalf of Bryan Banister <bbanister at jumptrading.com>
Reply-To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Date: Tuesday, March 7, 2017 at 3:17 PM
To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Subject: [EXTERNAL] Re: [gpfsug-discuss] Potential problems - leaving trace enabled in over-write mode?
Just depends on how your problem is detected… is it in a log? Is it found by running a command (.e.g mm*)? Is it discovered in `ps` output? Is your scheduler failing jobs?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20170307/454f9544/attachment.htm>
More information about the gpfsug-discuss
mailing list