Last Friday, one of our V880s kernel panicked with the following message.This is a SAN connected ZFS pool attached to one LUN. From this, it appears that the SAN 'disappeared' and then there was a panic shortly after.
Am I reading this correctly? Is this normal behavior for ZFS? This is a mostly patched Solaris 10 6/06 install. Before patching this system we did have a couple of NFS related panics, always on Fridays! This is the fourth panic, first time with a ZFS error. There are no errors in zpool status. Dec 1 20:30:21 foobar scsi: [ID 107833 kern.warning] WARNING: /[EMAIL PROTECTED],600000/[EMAIL PROTECTED]/[EMAIL PROTECTED],1 (sd17): Dec 1 20:30:21 foobar SCSI transport failed: reason 'incomplete': retrying command Dec 1 20:30:21 foobar scsi: [ID 107833 kern.warning] WARNING: /[EMAIL PROTECTED],600000/[EMAIL PROTECTED]/[EMAIL PROTECTED],1 (sd17): Dec 1 20:30:21 foobar SCSI transport failed: reason 'incomplete': retrying command Dec 1 20:30:21 foobar scsi: [ID 107833 kern.warning] WARNING: /[EMAIL PROTECTED],600000/[EMAIL PROTECTED]/[EMAIL PROTECTED],1 (sd17): Dec 1 20:30:21 foobar disk not responding to selection Dec 1 20:30:21 foobar scsi: [ID 107833 kern.warning] WARNING: /[EMAIL PROTECTED],600000/[EMAIL PROTECTED]/[EMAIL PROTECTED],1 (sd17): Dec 1 20:30:21 foobar disk not responding to selection Dec 1 20:30:21 foobar scsi: [ID 107833 kern.warning] WARNING: /[EMAIL PROTECTED],600000/[EMAIL PROTECTED]/[EMAIL PROTECTED],1 (sd17): Dec 1 20:30:21 foobar disk not responding to selection Dec 1 20:30:21 foobar scsi: [ID 107833 kern.warning] WARNING: /[EMAIL PROTECTED],600000/[EMAIL PROTECTED]/[EMAIL PROTECTED],1 (sd17): Dec 1 20:30:21 foobar disk not responding to selection Dec 1 20:30:22 foobar scsi: [ID 107833 kern.warning] WARNING: /[EMAIL PROTECTED],600000/[EMAIL PROTECTED]/[EMAIL PROTECTED],1 (sd17): Dec 1 20:30:22 foobar disk not responding to selection Dec 1 20:30:22 foobar unix: [ID 836849 kern.notice] Dec 1 20:30:22 foobar ^Mpanic[cpu2]/thread=2a100aedcc0: Dec 1 20:30:22 foobar unix: [ID 809409 kern.notice] ZFS: I/O failure (write on <unknown> off 0: zio 3004c0ce540 [L0 unallocated] 20000L/20000P DVA [0]=<0:2ae1900000:20000> fletcher2 uncompressed BE contiguous birth=586818 fill=0 cksum=102297a2db39dfc:cc8e38087da7a38f:239520856ececf15:c2fd36 9cea9db4a1): error 5 Dec 1 20:30:22 foobar unix: [ID 100000 kern.notice] Dec 1 20:30:22 foobar genunix: [ID 723222 kern.notice] 000002a100aed740 zfs:zio_done+284 (3004c0ce540, 0, a8, 70513bf0, 0, 60001374940) Dec 1 20:30:22 foobar genunix: [ID 179002 kern.notice] %l0-3: 000003006319fc80 0000000070513800 0000000000000005 0000000000000005 Dec 1 20:30:22 foobar %l4-7: 000000007b224278 0000000000000002 000000000008f442 0000000000000005 Dec 1 20:30:22 foobar genunix: [ID 723222 kern.notice] 000002a100aed940 zfs:zio_vdev_io_assess+178 (3004c0ce540, 8000, 10, 0, 0, 10) Dec 1 20:30:22 foobar genunix: [ID 179002 kern.notice] %l0-3: 0000000000000002 0000000000000001 0000000000000000 0000000000000005 Dec 1 20:30:22 foobar %l4-7: 0000000000000010 0000000035a536bc 0000000000000000 00043d7293172cfc Dec 1 20:30:22 foobar genunix: [ID 723222 kern.notice] 000002a100aeda00 genunix:taskq_thread+1a4 (600012a0c38, 600012a0be0, 50001, 43d72c8bfb810, 2a100aedaca, 2a100aedac8) Dec 1 20:30:22 foobar genunix: [ID 179002 kern.notice] %l0-3: 0000000000010000 00000600012a0c08 00000600012a0c10 00000600012a0c12 Dec 1 20:30:22 foobar %l4-7: 0000030060946320 0000000000000002 0000000000000000 00000600012a0c00 Dec 1 20:30:22 foobar unix: [ID 100000 kern.notice] Dec 1 20:30:22 foobar genunix: [ID 672855 kern.notice] syncing file systems... _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
