<html><body><p>You are correct. There is some level of tracing on the v7000U. <br>Also, if the gpfs daemon hits an assert or signal and tracing is running then traces are recycled automatically. There is no need to have another script monitoring for such events. You probably want to have mmtracectl --trace-recycle=global so that an assert on one node grabs traces on all nodes (ie fs manager). <br>As for performance, this one is more difficult and I don't have details. I can ping a colleague to see if he has numbers. Obviously there will be a performance penalty for running tracing. <br><br><br>Steve Duersch<br>Spectrum Scale<br>IBM Poughkeepsie, New York<br><br><br><br><br><tt>> <br>> <br>> ----------------------------------------------------------------------<br>> <br>> Message: 1<br>> Date: Tue, 7 Mar 2017 21:11:33 +0000<br>> From: "Oesterlin, Robert" <Robert.Oesterlin@nuance.com><br>> To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org><br>> Subject: Re: [gpfsug-discuss] Potential problems - leaving trace<br>> enabled in over-write mode?<br>> Message-ID: <FF476173-947E-461F-8223-CD0334E60FB1@nuance.com><br>> Content-Type: text/plain; charset="utf-8"<br>> <br>> I?ve been told that V70o0 unified nodes (GPFS under the covers) run <br>> with tracing enabled all the time.. but I agree with you Brian on <br>> the potential impacts. But when you must catch a trace for a problem<br>> that occurs once every few weeks ? how else would I do it?<br>> <br>> Bob Oesterlin<br>> Sr Principal Storage Engineer, Nuance<br>> 507-269-0413<br>> <br></tt><BR>
</body></html>