Thanks Henrik,<div>But I still see the problem, please see the following alert came from xymon a week or so ago.....</div><div><br></div><div><p class="MsoPlainText">red Su] Aug 22 01:26:51 EDT 2010 - Filesystems NOT ok
&red 21% / (20461936% used) has reached the PANIC level (95%) &red 1%
/app (65009052% used) has reached the PANIC level (95%) &red 1% /home
(112112360% used) has reached the PANIC level (95%) &red 6% /var (8933348%
used) has reached the PANIC level (95%) &red 1% /tmp (18638136% used) has
reached the PANIC level (95%) &red 49% /boot (48938% used) has reached the
PANIC level (95%) &red 11% /u01 (218810168% used) has reached the PANIC
level (95%) &red 7% /u04 (228560164% used) has reached the PANIC level
(95%) &red 35% /u02 (1154279480% used) has reached the PANIC level (95%)
&red 24% /old_u02 (1507070236% used) has reached the PANIC level (95%)</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Filesystem<span style="mso-spacerun:yes">
</span>1</p>
<p class="MsoPlainText">24-]locks<span style="mso-spacerun:yes"> </span><span style="mso-spacerun:yes"> </span>Used Available Capacity Mounted on</p>
<p class="MsoPlainText">/dev/sda5<span style="mso-spacerun:yes">
</span>27054004<span style="mso-spacerun:yes"> </span>5195620<span style="mso-spacerun:yes"> </span>20461936<span style="mso-spacerun:yes">
</span>21% /</p>
<p class="MsoPlainText">/dev/sdb1<span style="mso-spacerun:yes">
</span>68814716<span style="mso-spacerun:yes"> </span>253696<span style="mso-spacerun:yes"> </span>65009052<span style="mso-spacerun:yes">
</span>1% /app</p>
<p class="MsoPlainText">/dev/sdc2<span style="mso-spacerun:yes">
</span>118417044<span style="mso-spacerun:yes"> </span>192356 112112360<span style="mso-spacerun:yes"> </span>1% /home</p>
<p class="MsoPlainText">/dev/sda3<span style="mso-spacerun:yes">
</span>9920624<span style="mso-spacerun:yes"> </span>475208<span style="mso-spacerun:yes"> </span>8933348<span style="mso-spacerun:yes">
</span>6% /var</p>
<p class="MsoPlainText">/dev/sdc1<span style="mso-spacerun:yes">
</span>19840892<span style="mso-spacerun:yes"> </span>178616<span style="mso-spacerun:yes"> </span>18638136<span style="mso-spacerun:yes">
</span>1% /tmp</p>
<p class="MsoPlainText">/dev/sda1<span style="mso-spacerun:yes">
</span>101086<span style="mso-spacerun:yes"> </span>46929<span style="mso-spacerun:yes"> </span>48938<span style="mso-spacerun:yes">
</span>49% /boot</p>
<p class="MsoPlainText">/dev/mapper/VolGroup01-u01 258022788<span style="mso-spacerun:yes"> </span>26105832 218810168<span style="mso-spacerun:yes"> </span><span style="mso-spacerun:yes"> </span>11%
/u01</p>
<p class="MsoPlainText">/dev/mapper/VolGroup04-u04 258022788<span style="mso-spacerun:yes"> </span>16355836 228560164<span style="mso-spacerun:yes"> </span>7% /u04</p>
<p class="MsoPlainText">/dev/mapper/VolGroup03-u03 1857784872 609135396
1154279480<span style="mso-spacerun:yes"> </span>35% /u02</p>
<p class="MsoPlainText">/dev/mapper/VolGroup02-u02 2064204960 452279172
1507070236<span style="mso-spacerun:yes"> </span>24% /old_u02</p><br><div class="gmail_quote">On Thu, Sep 23, 2010 at 3:45 PM, Henrik Størner <span dir="ltr"><<a href="mailto:henrik@hswn.dk">henrik@hswn.dk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">This is a somewhat old post, but I'm responding anyway ...<br>
<div class="im"><br>
In <<a href="mailto:AANLkTinFdgiz2ie3NCxhuop8picZj6izZPdH6fESQfif@mail.gmail.com">AANLkTinFdgiz2ie3NCxhuop8picZj6izZPdH6fESQfif@mail.gmail.com</a>> Steve Holmes <<a href="mailto:sholmes42@mac.com">sholmes42@mac.com</a>> writes:<br>
<br>
>>>> Please see below, there is a problem with disk monitoring on one of the<br>
>>>> server. Can some one tell me if I did something wrong?<br>
>>>><br>
>>>> W]d Jul 28 10:34:31 EDT 2010 - Filesystems NOT ok<br>
>>>><br>
>>>> 7% / (8816628% used) has reached the PANIC level (95%)<br>
>>>> 38% /u01 (90371708% used) has reached the PANIC level (95%)<br>
>>>><br>
</div><div class="im">>>>> Filesystem 10<br>
>>>> 4-b]ocks Used Available Capacity Mounted on<br>
>>>> /dev/sda9 9920592 591896 8816628 7% /<br>
>>>> /dev/sda10 152435112 54195172 90371708 38% /u01<br>
>>>> /dev/sda8 9920592 154056 9254468 2% /tmp<br>
<br>
</div><div class="im">>It appears that Xymon has slipped one field to the left in parsing the df<br>
>output. The string at the beginning of each of the lines before the actual<br>
>df ouput should be the name of the filesystem (plus an icon, but we'll<br>
>ignore that for now). Then it is using the available number as the percent<br>
>used, which, of course, is huge.<br>
<br>
>I don't know if this is causing the problem but there is some funkiness with<br>
>the first line of the df output. It is broken between the 10 and the 4 and<br>
>there is a ']' instead of an 'l' in the word "blocks". Maybe this is a<br>
>cut/paste error, but if not, it is certainly not right.<br>
<br>
<br>
</div>There is a bug somewhere in the Xymon 4.3.0-beta code with the "df"<br>
status handling. I've seen it cause random RRD files to appear for<br>
systems that don't have such filesystems, and occasionally it would<br>
also result in this behaviour where a disk status goes wild.<br>
<br>
I haven't been able to nail it yet, mostly because it seems to happen<br>
very rarely and completely without any pattern. It would seem like<br>
some sort of memory corruption problem, but I've had the client-message<br>
handler running for days with valgrind (memory access checker) enabled,<br>
and it came up with nothing.<br>
<br>
Very annoying.<br>
<br>
<br>
Regards,<br>
Henrik<br>
<br>
<br>
To unsubscribe from the xymon list, send an e-mail to<br>
<a href="mailto:xymon-unsubscribe@xymon.com">xymon-unsubscribe@xymon.com</a><br>
<br>
<br>
</blockquote></div><br><br clear="all"><br>-- <br>Shailesh K. Paudyal<br><a href="mailto:shailesh.paudyal@gmail.com">shailesh.paudyal@gmail.com</a><br>
</div>