Thanks Richard
will go with fmdump for deeper insights - what we have now - but that's a
little "strange"
I post a "snippet" here ..... any ideas on this?
TIME CLASS
May 26 2015 09:36:49.120465328 ereport.io.scsi.cmd.disk.dev.rqs.derr
nvlist version: 0
class = ereport.io.scsi.cmd.disk.dev.rqs.derr
ena = 0xc70e06ca6eb03401
detector = (embedded nvlist)
nvlist version: 0
version = 0x0
scheme = dev
device-path =
/pci@79,0/pci8086,e08@3/pci1000,3040@0/iport@f/disk@w5000a72a3008bdfe,0
devid = id1,sd@n5000a7203008bdfe
(end detector)
devid = id1,sd@n5000a7203008bdfe
driver-assessment = fail
op-code = 0x15
cdb = 0x15 0x11 0x0 0x0 0x20 0x0
pkt-reason = 0x0
pkt-state = 0x3f
pkt-stats = 0x0
stat-code = 0x2
key = 0x5
asc = 0x26
ascq = 0x0
sense-data = 0x70 0x0 0x5 0x0 0x0 0x0 0x0 0x18
__ttl = 0x1
__tod = 0x55642291 0x72e27b0
May 26 2015 09:36:49.153548519 ereport.io.scsi.cmd.disk.dev.rqs.merr
nvlist version: 0
class = ereport.io.scsi.cmd.disk.dev.rqs.merr
ena = 0xc70e2657d9800801
detector = (embedded nvlist)
nvlist version: 0
version = 0x0
scheme = dev
device-path =
/pci@79,0/pci8086,e02@1/pci10df,f100@0/fp@0,0/disk@w10000090fa454abc,41
devid = id1,sd@n600144f0908ac7275000a7203008be03
(end detector)
devid = id1,sd@n600144f0908ac7275000a7203008be03
driver-assessment = fatal
op-code = 0x15
cdb = 0x15 0x11 0x0 0x0 0x18 0x0
pkt-reason = 0x0
pkt-state = 0x3f
pkt-stats = 0x0
stat-code = 0x2
key = 0x3
asc = 0xc
ascq = 0x0
sense-data = 0x70 0x0 0x3 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0xc 0x0
0x0 0x0 0x0 0x0
lba = 0x0
__ttl = 0x1
__tod = 0x55642291 0x926f6e7
May 26 2015 09:36:49.154109186 ereport.io.scsi.cmd.disk.dev.rqs.derr
nvlist version: 0
class = ereport.io.scsi.cmd.disk.dev.rqs.derr
ena = 0xc70e26e09d500801
detector = (embedded nvlist)
nvlist version: 0
version = 0x0
scheme = dev
device-path =
/pci@79,0/pci8086,e02@1/pci10df,f100@0,1/fp@0,0/disk@w10000090fa454abd,41
devid = id1,sd@n600144f0908ac7275000a7203008be03
(end detector)
devid = id1,sd@n600144f0908ac7275000a7203008be03
driver-assessment = retry
op-code = 0x28
cdb = 0x28 0x0 0x0 0x0 0x3 0x10 0x0 0x0 0x10 0x0
pkt-reason = 0x0
pkt-state = 0x3f
pkt-stats = 0x0
stat-code = 0x2
key = 0x6
asc = 0x29
ascq = 0x0
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 = 0x55642291 0x92f8502
May 26 2015 09:36:49.160466329 ereport.io.scsi.cmd.disk.dev.rqs.derr
nvlist version: 0
class = ereport.io.scsi.cmd.disk.dev.rqs.derr
ena = 0xc70e2cf119900401
detector = (embedded nvlist)
nvlist version: 0
version = 0x0
scheme = dev
device-path =
/pci@0,0/pci8086,e04@2/pci1000,3040@0/iport@f/disk@w5000a72b3008bdfe,0
devid = id1,sd@n5000a7203008bdfe
(end detector)
devid = id1,sd@n5000a7203008bdfe
driver-assessment = fail
op-code = 0x15
cdb = 0x15 0x11 0x0 0x0 0x20 0x0
pkt-reason = 0x0
pkt-state = 0x3f
pkt-stats = 0x0
stat-code = 0x2
key = 0x5
asc = 0x26
ascq = 0x0
sense-data = 0x70 0x0 0x5 0x0 0x0 0x0 0x0 0x18
__ttl = 0x1
__tod = 0x55642291 0x9908599
May 26 2015 09:36:49.154106525 ereport.io.scsi.cmd.disk.recovered
nvlist version: 0
class = ereport.io.scsi.cmd.disk.recovered
ena = 0xc70e26e09d500801
detector = (embedded nvlist)
nvlist version: 0
version = 0x0
scheme = dev
device-path =
/pci@79,0/pci8086,e02@1/pci10df,f100@0,1/fp@0,0/disk@w10000090fa454abd,41
devid = id1,sd@n600144f0908ac7275000a7203008be03
(end detector)
devid = id1,sd@n600144f0908ac7275000a7203008be03
driver-assessment = recovered
op-code = 0x28
cdb = 0x28 0x0 0x0 0x0 0x3 0x10 0x0 0x0 0x10 0x0
pkt-reason = 0x0
pkt-state = 0x1f
pkt-stats = 0x0
__ttl = 0x1
__tod = 0x55642291 0x92f7a9d
May 26 2015 09:36:49.200229651 ereport.io.scsi.cmd.disk.dev.rqs.merr
nvlist version: 0
class = ereport.io.scsi.cmd.disk.dev.rqs.merr
ena = 0xc70e52dda3800801
detector = (embedded nvlist)
nvlist version: 0
version = 0x0
scheme = dev
device-path =
/pci@79,0/pci8086,e02@1/pci10df,f100@0,1/fp@0,0/disk@w10000090fa454c6f,41
devid = id1,sd@n600144f0908ac7275000a7203008bdfe
(end detector)
devid = id1,sd@n600144f0908ac7275000a7203008bdfe
driver-assessment = fatal
op-code = 0x15
cdb = 0x15 0x11 0x0 0x0 0x18 0x0
pkt-reason = 0x0
pkt-state = 0x3f
pkt-stats = 0x0
stat-code = 0x2
key = 0x3
asc = 0xc
ascq = 0x0
sense-data = 0x70 0x0 0x3 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0xc 0x0
0x0 0x0 0x0 0x0
lba = 0x0
__ttl = 0x1
__tod = 0x55642291 0xbef4313
May 26 2015 09:36:49.200354141 ereport.io.scsi.cmd.disk.dev.rqs.derr
nvlist version: 0
class = ereport.io.scsi.cmd.disk.dev.rqs.derr
ena = 0xc70e52fc09700401
detector = (embedded nvlist)
nvlist version: 0
version = 0x0
scheme = dev
device-path =
/pci@79,0/pci8086,e02@1/pci10df,f100@0/fp@0,0/disk@w10000090fa454c6e,41
devid = id1,sd@n600144f0908ac7275000a7203008bdfe
(end detector)
devid = id1,sd@n600144f0908ac7275000a7203008bdfe
driver-assessment = retry
op-code = 0x28
cdb = 0x28 0x0 0x0 0x0 0x3 0x10 0x0 0x0 0x10 0x0
pkt-reason = 0x0
pkt-state = 0x3f
pkt-stats = 0x0
stat-code = 0x2
key = 0x6
asc = 0x29
ascq = 0x0
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 = 0x55642291 0xbf1295d
May 26 2015 09:36:49.200352640 ereport.io.scsi.cmd.disk.recovered
nvlist version: 0
class = ereport.io.scsi.cmd.disk.recovered
ena = 0xc70e52fc09700401
detector = (embedded nvlist)
nvlist version: 0
version = 0x0
scheme = dev
device-path =
/pci@79,0/pci8086,e02@1/pci10df,f100@0/fp@0,0/disk@w10000090fa454c6e,41
devid = id1,sd@n600144f0908ac7275000a7203008bdfe
(end detector)
devid = id1,sd@n600144f0908ac7275000a7203008bdfe
driver-assessment = recovered
op-code = 0x28
cdb = 0x28 0x0 0x0 0x0 0x3 0x10 0x0 0x0 0x10 0x0
pkt-reason = 0x0
pkt-state = 0x1f
pkt-stats = 0x0
__ttl = 0x1
__tod = 0x55642291 0xbf12380
May 26 2015 09:36:49.230402357 ereport.io.scsi.cmd.disk.dev.rqs.derr
nvlist version: 0
class = ereport.io.scsi.cmd.disk.dev.rqs.derr
ena = 0xc70e6fa487007c01
detector = (embedded nvlist)
nvlist version: 0
version = 0x0
scheme = dev
device-path =
/pci@79,0/pci8086,e02@1/pci10df,f100@0,1/fp@0,0/disk@w10000090fa454abd,5
devid = id1,sd@n600144f0908ac2055000c5005743d30f
(end detector)
devid = id1,sd@n600144f0908ac2055000c5005743d30f
driver-assessment = retry
op-code = 0x28
cdb = 0x28 0x0 0x0 0x0 0x1 0x20 0x0 0x0 0xe0 0x0
pkt-reason = 0x0
pkt-state = 0x3f
pkt-stats = 0x0
stat-code = 0x2
key = 0x6
asc = 0x29
ascq = 0x0
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 = 0x55642291 0xdbba935
May 26 2015 09:36:49.230395016 ereport.io.scsi.cmd.disk.dev.rqs.derr
nvlist version: 0
class = ereport.io.scsi.cmd.disk.dev.rqs.derr
ena = 0xc70e6fa487007c01
detector = (embedded nvlist)
nvlist version: 0
version = 0x0
scheme = dev
device-path =
/pci@79,0/pci8086,e02@1/pci10df,f100@0/fp@0,0/disk@w10000090fa454abc,5
devid = id1,sd@n600144f0908ac2055000c5005743d30f
(end detector)
devid = id1,sd@n600144f0908ac2055000c5005743d30f
driver-assessment = retry
op-code = 0x28
cdb = 0x28 0x0 0x0 0x0 0x1 0x20 0x0 0x0 0xe0 0x0
pkt-reason = 0x0
pkt-state = 0x3f
pkt-stats = 0x0
stat-code = 0x2
key = 0x6
asc = 0x29
ascq = 0x0
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 = 0x55642291 0xdbb8c88
May 26 2015 09:36:49.230386943 ereport.io.scsi.cmd.disk.recovered
nvlist version: 0
class = ereport.io.scsi.cmd.disk.recovered
ena = 0xc70e6fa487007c01
detector = (embedded nvlist)
nvlist version: 0
version = 0x0
scheme = dev
device-path =
/pci@79,0/pci8086,e02@1/pci10df,f100@0,1/fp@0,0/disk@w10000090fa454abd,5
devid = id1,sd@n600144f0908ac2055000c5005743d30f
(end detector)
2015-06-02 14:48 GMT+02:00 Richard Elling <[email protected]>
:
> question below...
>
> On Jun 1, 2015, at 9:37 PM, Michael Widmann <[email protected]>
> wrote:
>
>
> Hopefully someone can help on this maybe "bug" ?
> I've read about something like that from Robert Mustacchi ...
>
>
> Here's the config:
>
> Quadmirror ZFS: 2 Discs in DC1 / 2 Discs in DC2 (works perfect for
> Metro Style Cluster)
>
> If we use iSCSI Disc on this config we get the following: (checked in
> this config and even on the same box)
>
> Here's the error:
>
> c0t600144F0908AC7035000C5005750CEF7d0 Soft Errors: 0 Hard Errors: 10
> Transport Errors: 0
>
> Vendor: SEAGATE Product: ST2000NM0023 Revision: 1.0 Serial No: Z1X0Z1GS
> Size: 2000.40GB <2000398868480 bytes>
>
> Media Error: 0 Device Not Ready: 0 No Device: 10 Recoverable: 0
>
> Illegal Request: 0 Predictive Failure Analysis: 0
>
>
> c0t600144F0908AC7025000C5005715B7A3d0 Soft Errors: 0 Hard Errors: 10
> Transport Errors: 0
>
> Vendor: SEAGATE Product: ST2000NM0023 Revision: 1.0 Serial No: Z1X0KPAX
> Size: 2000.40GB <2000398868480 bytes>
>
> Media Error: 0 Device Not Ready: 0 No Device: 10 Recoverable: 0
>
> Illegal Request: 0 Predictive Failure Analysis: 0
>
>
> c0t600144F0908AC7015000C5005743530Bd0 Soft Errors: 0 Hard Errors: 10
> Transport Errors: 0
>
> Vendor: SEAGATE Product: ST2000NM0023 Revision: 1.0 Serial No: Z1X0WQA0
> Size: 2000.40GB <2000398868480 bytes>
>
> Media Error: 0 Device Not Ready: 0 No Device: 10 Recoverable: 0
>
> Illegal Request: 0 Predictive Failure Analysis: 0
>
>
> c0t600144F0908AC7275000A7203008BE03d0 Soft Errors: 0 Hard Errors: 9
> Transport Errors: 0
>
> Vendor: STEC Product: ZeusRAM Revision: 1.0 Serial No: STM000185B19 Size:
> 8.00GB <7999934464 bytes>
>
> Media Error: 4 Device Not Ready: 0 No Device: 5 Recoverable: 0 Illegal
> Request: 0 Predictive Failure Analysis: 0
>
> General troubleshooting tip:
> These are generic summary error reports. The detailed reports, including
> commands sent that
> received errors and the SCSI reply are recorded by FMA. Use "fmdump -eV"
> for a verbose listing
> of the error reports.
>
> More specific tip:
> These are also all local disks, no iSCSI involved. The hard/soft/transport
> error counters are higher-level than
> the more detailed error counters: media, DNR, recoverable, etc. "No
> device" means the device wasn't there
> when a SCSI command was issued to it. These are categorized as "hard"
> errors, so you'll see both counters
> increment.
>
>
>
> zpool import send an SCSI_RESERVATION Command to the Discs to claim it,
> this is answered with an SCSI_RESET_TARGET (sic!!!)
>
>
> zpool import knows nothing about disks, so it cannot issue a SCSI
> reservation. However, if a devices is not
> responding, or has been reserved away from the node with SCSI-2
> reservation, then the sd driver can issue
> a target reset to the device. The answer lies in the detailed FME ereports.
>
>
> There's no SCSI_RESET_LUN in the iSCSI Specs - so during Initialize and
> reading configs of Discs the STMF Target got resetted (each disc in DC1 and
> DC2) - for some IOPS ....
>
>
> SCSI_RESET_LUN is an sd driver notion. It is equivalent to sending the
> appropriate reset command to a
> LUN. For simple SCSI disks, this is the same as a target reset.
> -- richard
>
>
> That seems to be a bug - as it couldn't really be a wanted feature :-)
>
>
>
> What we tried for testing:
> There are no errors on SAS Discs (physical)
> zpool import / export works
> BIOS on each disc is the same
>
> The error just occurs on "import and create (not during operation on the
> metro cluster) "
>
> Any idea on this?
>
> Thanks in advance
>
> Mike Tomaselli
> *smartos-discuss* | Archives
> <https://www.listbox.com/member/archive/184463/=now>
> <https://www.listbox.com/member/archive/rss/184463/21953302-fd56db47> |
> Modify <https://www.listbox.com/member/?&;> Your Subscription
> <http://www.listbox.com/>
>
>
> *smartos-discuss* | Archives
> <https://www.listbox.com/member/archive/184463/=now>
> <https://www.listbox.com/member/archive/rss/184463/22379235-70c1827a> |
> Modify
> <https://www.listbox.com/member/?&;>
> Your Subscription <http://www.listbox.com>
>
--
bayoda.com - DataStorage and Backup
by nimbus Development IT Consulting GmbH
-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription:
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com
