`<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 6, 2016, at 8:16 PM, Lawrence Giam <<a href="mailto:paladinemishakal@gmail.com" class="">paladinemishakal@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi All,<div class=""><br class=""></div><div class="">Also to note that I have another running OpenIndiana 151a7 and this is also a SuperMicro server, this has the same behaviour which is the system keep generating the resource.sysevent.EC_hba.ESC_sas_hba_port_broadcast message and getting logged into infolog_hival but one thing different is that the logadm is doing it's job of rotating the log.</div><div class=""><br class=""></div><div class="">On the system running OmniOS, I have compare the logadm.conf on both OpenIndiana and OmniOS and there are identical but OmniOS is not rotating this particular log. Is there any way I can check what is wrong? Why logadm is not rotating the infolog_hival when the filesize reach greater than 10m ?</div></div></div></blockquote><div><br class=""></div><div>Under heavy writes, logadm won’t rotate the logs.</div><div><br class=""></div><div>You might need to disable the port. We’ve seen cases where miswired SAS connections</div><div>that are not disabled by default in the firmware cause spurious interrupts. This can be done</div><div>with various tools, depending on which port is complaining. For example, in smp_utils, </div><div>smp_phy_control allows you to send link control commands to expanders. However, the</div><div>only real cure is hardware/firmware.</div><div> — richard</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><br class=""></div><div class="">This is the setting of logadm.conf from OpenIndiana 151a7:</div><div class="">/var/fm/fmd/infolog_hival -N -A 2y -S 50m -s 10m -M '/usr/sbin/fmadm -q rotate infolog_hival && mv /var/fm/fmd/infolog_hival.0- $nfile'<br class=""></div><div class=""><br class=""></div><div class="">Looking into /var/logadm/timestamps</div><div class=""><div class=""># This file holds internal data for logadm(1M).</div><div class=""># Do not edit.</div><div class="">/var/log/syslog -P 'Sat Dec 3 19:10:00 2016'</div><div class="">/var/adm/messages -P 'Wed Oct 26 19:10:00 2016'</div><div class="">/var/cron/log -P 'Sat Jun 25 19:10:00 2016'</div><div class="">/var/fm/fmd/infolog_hival -P 'Mon Dec 5 19:10:00 2016'</div><div class="">/var/adm/wtmpx -P 'Wed Oct 5 19:10:00 2016'</div></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">This is the setting of logadm.conf from OmniOS R151014:</div><div class="">/var/fm/fmd/infolog_hival -N -A 2y -S 50m -s 10m -M '/usr/sbin/fmadm -q rotate infolog_hival && mv /var/fm/fmd/infolog_hival.0- $nfile'<br class=""></div><div class=""><br class=""></div><div class="">Looking into /var/logadm/timestamps</div><div class=""><div class=""># This file holds internal data for logadm(1M).</div><div class=""># Do not edit.</div><div class="">/var/adm/messages -P 'Tue Dec 6 19:10:00 2016'</div><div class="">/var/cron/log -P 'Thu Nov 24 19:10:00 2016'</div><div class="">/var/svc/log/system-idmap:default.log -P 'Tue Dec 8 19:10:00 2015'</div></div><div class=""><br class=""></div><div class="">Cron is set to run logadm everyday at 03:10 am.</div><div class=""><br class=""></div><div class="">Regards.</div><div class=""><br class=""></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Tue, Nov 29, 2016 at 12:16 PM, Lawrence Giam <span dir="ltr" class=""><<a href="mailto:paladinemishakal@gmail.com" target="_blank" class="">paladinemishakal@gmail.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="">Hi All,<div class=""><br class=""></div><div class="">I have a Supermicro box running OmniOS R151014 build 170cea2. </div><div class="">I am getting a lot of entries in infolog_hival about resource.sysevent.EC_<wbr class="">hba.ESC_sas_hba_port_broadcast</div><div class=""><br class=""></div><div class=""><div class="">lawrence@sgsan1n2:/var/fm/fmd$ fmdump -I</div><div class="">Nov 29 08:45:33.0893 resource.sysevent.EC_hba.ESC_<wbr class="">sas_hba_port_broadcast</div><div class="">Nov 29 08:45:33.0893 resource.sysevent.EC_hba.ESC_<wbr class="">sas_hba_port_broadcast</div><div class="">Nov 29 08:45:33.0893 resource.sysevent.EC_hba.ESC_<wbr class="">sas_hba_port_broadcast</div><div class=""><br class=""></div><div class="">lawrence@sgsan1n2:/var/fm/fmd$ fmdump -IV</div><div class="">Nov 29 2016 03:12:20.907712302 (absent)</div><div class="">nvlist version: 0</div><div class="">driver_instance = 0</div><div class="">port_address = w500304800bfc5c02</div><div class="">devfs_path = /pci@0,0/pci8086,340c@5/<wbr class="">pci15d9,400@0</div><div class="">PhyIdentifier = 0x2</div><div class="">event_type = port_broadcast_ses</div><div class="">class = resource.sysevent.EC_hba.ESC_<wbr class="">sas_hba_port_broadcast</div><div class="">version = 0x0</div><div class="">__ttl = 0x1</div><div class="">__tod = 0x583c8194 0x361a972e</div><div class=""><br class=""></div><div class="">Nov 29 2016 03:12:20.907718074 (absent)</div><div class="">nvlist version: 0</div><div class="">driver_instance = 0</div><div class="">port_address = w500304800bfc5c03</div><div class="">devfs_path = /pci@0,0/pci8086,340c@5/<wbr class="">pci15d9,400@0</div><div class="">PhyIdentifier = 0x3</div><div class="">event_type = port_broadcast_ses</div><div class="">class = resource.sysevent.EC_hba.ESC_<wbr class="">sas_hba_port_broadcast</div><div class="">version = 0x0</div><div class="">__ttl = 0x1</div><div class="">__tod = 0x583c8194 0x361aadba</div></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">This is a chassic with 2 motherboard sharing a single backbone, each motherboard accessing it's own set of disks and we have a HA solution to auto-mount the disks to the other motherboard should there be a problem with the motherboard.</div><div class=""><br class=""></div><div class="">IS it possible to disable them?</div><div class=""><br class=""></div><div class="">Thanks & Regards.</div></div>
</blockquote></div><br class=""></div>
_______________________________________________<br class="">OmniOS-discuss mailing list<br class=""><a href="mailto:OmniOS-discuss@lists.omniti.com" class="">OmniOS-discuss@lists.omniti.com</a><br class="">http://lists.omniti.com/mailman/listinfo/omnios-discuss<br class=""></div></blockquote></div><br class=""></body></html>`