<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" id="owaParaStyle">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body fpstyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">
<div>Indeed,</div>
<div>I just realized that after last recent update to dssg-2.0a ntpd is crashing very frequently.</div>
<div>Thanks for the hint.</div>
<div><br>
</div>
<div> Alvise</div>
<div><br>
</div>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div id="divRpF142743" style="direction: ltr;"><font size="2" face="Tahoma" color="#000000"><b>From:</b> gpfsug-discuss-bounces@spectrumscale.org [gpfsug-discuss-bounces@spectrumscale.org] on behalf of Olaf Weiser [olaf.weiser@de.ibm.com]<br>
<b>Sent:</b> Thursday, November 15, 2018 9:35 PM<br>
<b>To:</b> gpfsug main discussion list<br>
<b>Subject:</b> Re: [gpfsug-discuss] Wrong behavior of mmperfmon<br>
</font><br>
</div>
<div></div>
<div><font size="2" face="sans-serif">ntp running / time correct ?</font><br>
<br>
<br>
<br>
<br>
<br>
<font size="1" face="sans-serif" color="#5f5f5f">From: </font><font size="1" face="sans-serif">"Dorigo Alvise (PSI)" <alvise.dorigo@psi.ch></font><br>
<font size="1" face="sans-serif" color="#5f5f5f">To: </font><font size="1" face="sans-serif">"gpfsug-discuss@spectrumscale.org" <gpfsug-discuss@spectrumscale.org></font><br>
<font size="1" face="sans-serif" color="#5f5f5f">Date: </font><font size="1" face="sans-serif">11/15/2018 04:30 PM</font><br>
<font size="1" face="sans-serif" color="#5f5f5f">Subject: </font><font size="1" face="sans-serif">[gpfsug-discuss] Wrong behavior of mmperfmon</font><br>
<font size="1" face="sans-serif" color="#5f5f5f">Sent by: </font><font size="1" face="sans-serif">gpfsug-discuss-bounces@spectrumscale.org</font><br>
<hr noshade="">
<br>
<br>
<br>
<font size="2" face="Tahoma">Hello,</font><br>
<font size="2" face="Tahoma">I'm using mmperfmon to get writing stats on NSD during a write activity on a GPFS filesystem (Lenovo system with dss-g-2.0a).</font><br>
<br>
<font size="2" face="Tahoma">I use this command:</font><br>
<br>
<font size="2" face="Tahoma"># mmperfmon query 'sf-dssio-1.psi.ch|GPFSNSDFS|RAW|gpfs_nsdfs_bytes_written' --number-buckets 48 -b 1</font><br>
<br>
<font size="2" face="Tahoma">to get the stats. What it returns is a list of valid values followed by a longer list of 'null' as shown below:</font><br>
<font size="2" face="Tahoma"><br>
Legend:<br>
1: sf-dssio-1.psi.ch|GPFSNSDFS|RAW|gpfs_nsdfs_bytes_written<br>
<br>
Row Timestamp gpfs_nsdfs_bytes_written <br>
1 2018-11-15-16:15:57 746586112 <br>
2 2018-11-15-16:15:58 704643072 <br>
3 2018-11-15-16:15:59 805306368 <br>
4 2018-11-15-16:16:00 754974720 <br>
5 2018-11-15-16:16:01 754974720 <br>
6 2018-11-15-16:16:02 763363328 <br>
7 2018-11-15-16:16:03 746586112 <br>
8 2018-11-15-16:16:04 746848256 <br>
9 2018-11-15-16:16:05 780140544 <br>
10 2018-11-15-16:16:06 679923712 <br>
11 2018-11-15-16:16:07 746618880 <br>
12 2018-11-15-16:16:08 780140544 <br>
13 2018-11-15-16:16:09 746586112 <br>
14 2018-11-15-16:16:10 763363328 <br>
15 2018-11-15-16:16:11 780173312 <br>
16 2018-11-15-16:16:12 721420288 <br>
17 2018-11-15-16:16:13 796917760 <br>
18 2018-11-15-16:16:14 763363328 <br>
19 2018-11-15-16:16:15 738197504 <br>
20 2018-11-15-16:16:16 738197504 <br>
21 2018-11-15-16:16:17 null <br>
22 2018-11-15-16:16:18 null <br>
23 2018-11-15-16:16:19 null <br>
24 2018-11-15-16:16:20 null <br>
25 2018-11-15-16:16:21 null <br>
26 2018-11-15-16:16:22 null <br>
27 2018-11-15-16:16:23 null <br>
28 2018-11-15-16:16:24 null <br>
29 2018-11-15-16:16:25 null <br>
30 2018-11-15-16:16:26 null <br>
31 2018-11-15-16:16:27 null <br>
32 2018-11-15-16:16:28 null <br>
33 2018-11-15-16:16:29 null <br>
34 2018-11-15-16:16:30 null <br>
35 2018-11-15-16:16:31 null <br>
36 2018-11-15-16:16:32 null <br>
37 2018-11-15-16:16:33 null <br>
38 2018-11-15-16:16:34 null <br>
39 2018-11-15-16:16:35 null <br>
40 2018-11-15-16:16:36 null <br>
41 2018-11-15-16:16:37 null <br>
42 2018-11-15-16:16:38 null <br>
43 2018-11-15-16:16:39 null <br>
44 2018-11-15-16:16:40 null <br>
45 2018-11-15-16:16:41 null <br>
46 2018-11-15-16:16:42 null <br>
47 2018-11-15-16:16:43 null <br>
48 2018-11-15-16:16:44 null </font><br>
<br>
<font size="2" face="Tahoma">If I run again and again I still get the same pattern: valid data (even 0 in case of not write activity) followed by more null data.</font><br>
<br>
<font size="2" face="Tahoma">Is that normal ? If not, is there a way to get only non-null data by fine-tuning pmcollector's configuration file ?</font><br>
<font size="2" face="Tahoma">The corresponding ZiMon sensor (GPFSNSDFS) have period=1.</font><br>
<font size="2" face="Tahoma">The ZiMon version is 4.2.3-7.</font><br>
<br>
<font size="2" face="Tahoma">Thanks,</font><br>
<br>
<font size="2" face="Tahoma"> Alvise</font><br>
<font size="2" face="Tahoma"> </font><tt><font size="2">_______________________________________________<br>
gpfsug-discuss mailing list<br>
gpfsug-discuss at spectrumscale.org<br>
</font></tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss" target="_blank" rel="noopener noreferrer"><tt><font size="2">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</font></tt></a><tt><font size="2"><br>
</font></tt><br>
<br>
<br>
</div>
</div>
</div>
</body>
</html>