Dear all,

I found the FMA Error on Solaris10 sparch system, capacity file
/var/fm/fmd/errlog experience increase every second, if in a total of one
day, log can write to more than 1GB. Automatically, space root is always
full (100%), so while errlog removed manually so that the system stable and
capacity disk space (27%).
The result of check :
*# fmdump -e* output :
Jan 1 09:22:19.1161 ereport.io.ddi.fm-capability
Jan 1 09:22:19.1161 ereport.io.ddi.fm-capability
Jan 1 09:22:19.1163 ereport.io.ddi.fm-capability
Jan 1 09:22:19.1163 ereport.io.ddi.fm-capability
Jan 1 09:22:19.1164 ereport.io.ddi.fm-capability
...looping...

*# fmdump -eV* output :
Jan 1 2011 09:22:19.116108400 ereport.io.ddi.fm-capability
nvlist version: 0
    class = ereport.io.ddi.fm-capability
    ena = 0x6b063c391e00401
    detector = (embedded nvlist)
    nvlist version: 0
        version = 0x0
        scheme = dev
        device-path = /
    (end detector)
    *dvr-name = fp*
    __ttl = 0x1
    __tod = 0x4bee055b 0x6ebac70
...looping...

*# fmadm faulty* output : null

*# svcs -l fmd* output :
fmri         svc:/system/fmd:default
name         Solaris Fault Manager
enabled      true
state        online
next_state   none
state_time   Wed Jan 05 14:04:29 2011
logfile      /var/svc/log/system-fmd:default.log
restarter    svc:/system/svc/restarter:default
contract_id  61
dependency   optional_all/none svc:/platform/sun4u/dscp (disabled)
dependency   require_all/none file://localhost/usr/lib/fm/fmd/fmd (online)
dependency   require_all/none svc:/system/sysevent (online)
svc:/system/filesystem/minimal (online) svc:/system/dumpadm (online)
dependency   optional_all/none svc:/network/rpc/bind (online)

*# less /var/adm/messages* already filtered from fmdump above :
Jan  2 04:13:04 solaris emlxs: [ID 349649 kern.info] [ B.1653]emlxs1:
NOTICE: 100: Driver attach. (Emulex-S s10-64 sparc v2.40s
(2009.07.17.10.15))
Jan  2 04:13:04 solaris emlxs: [ID 349649 kern.info] [ B.1656]emlxs1:
NOTICE: 100: Driver attach. (LP11002-S Dev_id:fc10 Sub_id:fc12 Id:20)
Jan  2 04:13:04 solaris emlxs: [ID 349649 kern.info] [ B.1663]emlxs1:
NOTICE: 100: Driver attach. (Firmware:2.80x5 (B3F2.80X5) Boot:5.01a9
Fcode:1.50a8)
Jan  2 04:13:04 solaris emlxs: [ID 349649 kern.info] [ B.1688]emlxs1:
NOTICE: 100: Driver attach. (SLI:3 MSI:1 NPIV:0 FCA)
Jan  2 04:13:04 solaris emlxs: [ID 349649 kern.info] [ B.168E]emlxs1:
NOTICE: 100: Driver attach. (WWPN:10000000C95555A3 WWNN:20000000C95555A3)
Jan  2 04:13:04 solaris px_pci: [ID 370704 kern.info] PCI-device:
SUNW,em...@2,1, emlxs1
Jan  2 04:13:04 solaris genunix: [ID 936769 kern.info] emlxs1 is /p...@1f
,700000/p...@0/SUNW,em...@2,1
Jan  2 04:13:04 solaris emlxs: [ID 349649 kern.info] [ B.063B]emlxs0:
NOTICE: 720: Link up. (4Gb, fabric)
Jan  2 04:13:04 solaris genunix: [ID 936769 kern.info] *fp*1 is /p...@1f
,700000/p...@0/SUNW,em...@2,1/*...@0,0
Jan  2 04:13:04 solaris genunix: [ID 936769 kern.info] *fp*2 is /p...@1f
,700000/p...@0/SUNW,em...@2/*...@0,0

I also attach the complete results messages dan syslog.

How to overcome this error? Does the kernel does not support the Emulex
driver?

Thankyou..



-- 
Regards,
#470708
_______________________________________________
Solaris-Users mailing list
Solaris-Users@filibeto.org
http://www.filibeto.org/mailman/listinfo/solaris-users

Reply via email to