AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20090414185556.0020bb7d@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:mail.onstor.net
NSV:
SSH:
R:<patrick.haverty@onstor.com>,<brian.stark@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@exch1.onstor.net/INBOX	0	102AB4F33EBBDB4C91915B145C8E9FB31284F9B479@exch1.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Tue, 14 Apr 2009 18:56:52 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: Patrick Haverty <patrick.haverty@onstor.com>
Cc: Brian Stark <brian.stark@onstor.com>
Subject: Re: FMA
Message-ID: <20090414185652.33483565@ripper.onstor.net>
In-Reply-To: <102AB4F33EBBDB4C91915B145C8E9FB31284F9B479@exch1.onstor.net>
References: <102AB4F33EBBDB4C91915B145C8E9FB31284F9B479@exch1.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Do you want me to reboot it to the last nmu checkpoint/snapshot?
Whatever that is?  It was created on april-06.


 On Tue, 14 Apr 2009 17:56:37 -0700 Patrick Haverty
<patrick.haverty@onstor.com> wrote:

> This, below, is what I see on Leo-4.  It is an event related to me pulling out a disk.  I did not see any activity in /var/adm/messages or in the NMS log (show appliance nms log) when I pull the plug on a power supply.  This seems to me to indicate we may get FM event notification from an unknown event on the SAS links, but may have to put together the piece to get local (in the head) hardware events transported to the FM deamon, or to get some sort of action on the unknown event (does FMA by default just put an entry into the messages file and then cannot be instructed to take a different action?).  The configuration shows that there is some tramnsport module for system events, but I'm clueless as to the from and to of the transport.  Maybe there are other modules in outer space, I mean open source, that would do the hardware events stuff, but I don't even know if those events get reported to the OS or ZFS in any way, shape, or form.
> 
> BTW, at this point I've hosed Leopard-7 to the point I can't even reboot.  That's why I'm looking at Leopard-4 for now.
> 
> root@Leopard-4:/volumes# fmdump
> TIME                 UUID                                 SUNW-MSG-ID
> Apr 14 09:36:12.0746 b53b0acb-0074-e560-e7ad-d2fd9c29da17 ZFS-8000-FD
> 
> 
> root@Leopard-4:/volumes# fmadm config
> MODULE                   VERSION STATUS  DESCRIPTION
> cpumem-retire            1.1     active  CPU/Memory Retire Agent
> disk-transport           1.0     active  Disk Transport Agent
> eft                      1.16    active  eft diagnosis engine
> fabric-xlate             1.0     active  Fabric Ereport Translater
> fmd-self-diagnosis       1.0     active  Fault Manager Self-Diagnosis
> io-retire                2.0     active  I/O Retire Agent
> nms-transport            1.0     active  NMS Messaging Agent
> sysevent-transport       1.0     active  SysEvent Transport Agent
> syslog-msgs              1.0     active  Syslog Messaging Agent
> zfs-diagnosis            1.0     active  ZFS Diagnosis Engine
> zfs-retire               1.0     active  ZFS Retire Agent
> 
