Ethan Erchinger wrote: > > > Richard Elling wrote: >> >> I've seen these symptoms when a large number of errors were reported >> in a short period of time and memory was low. What does "fmdump -eV" >> show? >> > fmdump -eV shows lots of messages like this, and yea, I believe that > to be sd16 which is the SSD: > > Dec 03 2008 08:31:11.224690595 ereport.io.scsi.cmd.disk.dev.rqs.derr > nvlist version: 0 > class = ereport.io.scsi.cmd.disk.dev.rqs.derr > ena = 0x76bbfe8ef9000c01 > detector = (embedded nvlist) > nvlist version: 0 > version = 0x0 > scheme = dev > device-path = /[EMAIL PROTECTED],0/pci10de,[EMAIL > PROTECTED]/pci1000,[EMAIL PROTECTED]/[EMAIL PROTECTED],0 > devid = id1,[EMAIL PROTECTED] > (end detector) > > driver-assessment = retry
We retry, which is why there is a recovery e-report later. > op-code = 0x2a > cdb = 0x2a 0x0 0x1 0xe8 0x20 0x88 0x0 0x0 0x3 0x0 > pkt-reason = 0x0 > pkt-state = 0x37 > pkt-stats = 0x0 > stat-code = 0x2 > key = 0x6 > asc = 0x29 > ascq = 0x0 ASC/ASCQ 29/00 is POWER ON, RESET, OR BUS DEVICE RESET OCCURRED http://www.t10.org/lists/asc-num.htm#ASC_29 [this should be more descriptive as the codes are, more-or-less, standardized, I'll try to file an RFE, unless someone beat me to it] Depending on which system did the reset, it should be noted in the /var/adm/messages log. This makes me suspect the hardware (firmware, actually). -- richard > sense-data = 0x70 0x0 0x6 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 > 0x29 0x0 0x0 0x0 0x0 0x0 0x0 0x0 > __ttl = 0x1 > __tod = 0x4936b44f 0xd6481a3 > > Dec 03 2008 08:31:11.224690595 ereport.io.scsi.cmd.disk.recovered > nvlist version: 0 > class = ereport.io.scsi.cmd.disk.recovered > ena = 0x76bbfe8ef9000c01 > detector = (embedded nvlist) > nvlist version: 0 > version = 0x0 > scheme = dev > device-path = /[EMAIL PROTECTED],0/pci10de,[EMAIL > PROTECTED]/pci1000,[EMAIL PROTECTED]/[EMAIL PROTECTED],0 > devid = id1,[EMAIL PROTECTED] > (end detector) > > driver-assessment = recovered > op-code = 0x2a > cdb = 0x2a 0x0 0x1 0xe8 0x20 0x88 0x0 0x0 0x3 0x0 > pkt-reason = 0x0 > pkt-state = 0x1f > pkt-stats = 0x0 > __ttl = 0x1 > __tod = 0x4936b44f 0xd6481a3 > >> Also, it would help to know what OS release you are using. > Oh, it was at the bottom of my original message, but I just realized > that I'm actually running snv_99, forgot that I had performed an > image-update a while back. > _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
