Re: iSCSI target not coming back up (was Fwd: [zfs-discuss] Re: snv63: kernel panic on import)
Nigel, Was the iSCSI target daemon running and the targets are gone? or did the daemon core repeatedly? How did you created the targets? -tim eric kustarz wrote: Hi Tim, Is the iSCSI target not coming back up after a reboot a known problem? Can you take a look? eric Begin forwarded message: From: eric kustarz <[EMAIL PROTECTED]> Date: May 16, 2007 8:56:44 AM PDT To: Nigel Smith <[EMAIL PROTECTED]> Cc: zfs-discuss@opensolaris.org Subject: Re: [zfs-discuss] Re: snv63: kernel panic on import On May 15, 2007, at 4:49 PM, Nigel Smith wrote: I seem to have got the same core dump, in a different way. I had a zpool setup on a iscsi 'disk'. For details see: http://mail.opensolaris.org/pipermail/storage-discuss/2007-May/001162.html But after a reboot the iscsi target was not longer available, so the iscsi initiator could not provide the disk that he zpool was based on. I did a 'zpool status', but the PC just rebooted, rather than handling it in a graceful way. After the reboot I discover a core dump has been created - details below: ZFS panic'ing on a failed write in a non-redundant pool is known and is being worked on. Why the iSCSI device didn't come up is also a bug. I'll ask the iSCSI people to take a look... eric # cat /etc/release Solaris Nevada snv_60 X86 Copyright 2007 Sun Microsystems, Inc. All Rights Reserved. Use is subject to license terms. Assembled 12 March 2007 # # cd /var/crash/solaris # mdb -k 1 Loading modules: [ unix genunix specfs dtrace uppc pcplusmp scsi_vhci ufs ip hook neti sctp arp usba uhci qlc fctl nca lofs zfs random md cpc crypto fcip fcp logindmux ptm sppp emlxs ipc ] ::status debugging crash dump vmcore.1 (64-bit) from solaris operating system: 5.11 snv_60 (i86pc) panic message: ZFS: I/O failure (write on off 0: zio fffec38cf340 [L0 packed nvlist] 4000L/600P DVA[0]=<0:160225800:600> DVA[1]=<0:9800:600> fletcher4 lzjb LE contiguous birth=192896 fill=1 cksum=6b28 dump content: kernel pages only *panic_thread::findstack -v stack pointer for thread ff00025b2c80: ff00025b28f0 ff00025b29e0 panic+0x9c() ff00025b2a40 zio_done+0x17c(fffec38cf340) ff00025b2a60 zio_next_stage+0xb3(fffec38cf340) ff00025b2ab0 zio_wait_for_children+0x5d(fffec38cf340, 11, fffec38cf598) ff00025b2ad0 zio_wait_children_done+0x20(fffec38cf340) ff00025b2af0 zio_next_stage+0xb3(fffec38cf340) ff00025b2b40 zio_vdev_io_assess+0x129(fffec38cf340) ff00025b2b60 zio_next_stage+0xb3(fffec38cf340) ff00025b2bb0 vdev_mirror_io_done+0x2af(fffec38cf340) ff00025b2bd0 zio_vdev_io_done+0x26(fffec38cf340) ff00025b2c60 taskq_thread+0x1a7(fffec154f018) ff00025b2c70 thread_start+8() ::cpuinfo -v ID ADDR FLG NRUN BSPL PRI RNRN KRNRN SWITCH THREAD PROC 0 fbc31f80 1b20 99 nono t-0 ff00025b2c80 sched || RUNNING <--++--> PRI THREAD PROC READY60 ff00022c9c80 sched EXISTS60 ff00020e9c80 sched ENABLE ID ADDR FLG NRUN BSPL PRI RNRN KRNRN SWITCH THREAD PROC 1 fffec11ad000 1f30 59 yesno t-0 fffec3dcbbc0 syslogd || RUNNING <--++--> PRI THREAD PROC READY60 ff000212bc80 sched QUIESCED59 fffec1e51360 syslogd EXISTS59 fffec1ec2180 syslogd ENABLE ::quit This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Re: snv63: kernel panic on import
On May 15, 2007, at 4:49 PM, Nigel Smith wrote: I seem to have got the same core dump, in a different way. I had a zpool setup on a iscsi 'disk'. For details see: http://mail.opensolaris.org/pipermail/storage-discuss/2007-May/ 001162.html But after a reboot the iscsi target was not longer available, so the iscsi initiator could not provide the disk that he zpool was based on. I did a 'zpool status', but the PC just rebooted, rather than handling it in a graceful way. After the reboot I discover a core dump has been created - details below: ZFS panic'ing on a failed write in a non-redundant pool is known and is being worked on. Why the iSCSI device didn't come up is also a bug. I'll ask the iSCSI people to take a look... eric # cat /etc/release Solaris Nevada snv_60 X86 Copyright 2007 Sun Microsystems, Inc. All Rights Reserved. Use is subject to license terms. Assembled 12 March 2007 # # cd /var/crash/solaris # mdb -k 1 Loading modules: [ unix genunix specfs dtrace uppc pcplusmp scsi_vhci ufs ip hook neti sctp arp usba uhci qlc fctl nca lofs zfs random md cpc crypto fcip fcp logindmux ptm sppp emlxs ipc ] ::status debugging crash dump vmcore.1 (64-bit) from solaris operating system: 5.11 snv_60 (i86pc) panic message: ZFS: I/O failure (write on off 0: zio fffec38cf340 [L0 packed nvlist] 4000L/600P DVA[0]=<0:160225800:600> DVA[1]=<0:9800:600> fletcher4 lzjb LE contiguous birth=192896 fill=1 cksum=6b28 dump content: kernel pages only *panic_thread::findstack -v stack pointer for thread ff00025b2c80: ff00025b28f0 ff00025b29e0 panic+0x9c() ff00025b2a40 zio_done+0x17c(fffec38cf340) ff00025b2a60 zio_next_stage+0xb3(fffec38cf340) ff00025b2ab0 zio_wait_for_children+0x5d(fffec38cf340, 11, fffec38cf598) ff00025b2ad0 zio_wait_children_done+0x20(fffec38cf340) ff00025b2af0 zio_next_stage+0xb3(fffec38cf340) ff00025b2b40 zio_vdev_io_assess+0x129(fffec38cf340) ff00025b2b60 zio_next_stage+0xb3(fffec38cf340) ff00025b2bb0 vdev_mirror_io_done+0x2af(fffec38cf340) ff00025b2bd0 zio_vdev_io_done+0x26(fffec38cf340) ff00025b2c60 taskq_thread+0x1a7(fffec154f018) ff00025b2c70 thread_start+8() ::cpuinfo -v ID ADDR FLG NRUN BSPL PRI RNRN KRNRN SWITCH THREAD PROC 0 fbc31f80 1b20 99 nono t-0 ff00025b2c80 sched || RUNNING <--++--> PRI THREAD PROC READY60 ff00022c9c80 sched EXISTS60 ff00020e9c80 sched ENABLE ID ADDR FLG NRUN BSPL PRI RNRN KRNRN SWITCH THREAD PROC 1 fffec11ad000 1f30 59 yesno t-0 fffec3dcbbc0 syslogd || RUNNING <--++--> PRI THREAD PROC READY60 ff000212bc80 sched QUIESCED59 fffec1e51360 syslogd EXISTS59 fffec1ec2180 syslogd ENABLE ::quit This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
[zfs-discuss] Re: snv63: kernel panic on import
I seem to have got the same core dump, in a different way. I had a zpool setup on a iscsi 'disk'. For details see: http://mail.opensolaris.org/pipermail/storage-discuss/2007-May/001162.html But after a reboot the iscsi target was not longer available, so the iscsi initiator could not provide the disk that he zpool was based on. I did a 'zpool status', but the PC just rebooted, rather than handling it in a graceful way. After the reboot I discover a core dump has been created - details below: # cat /etc/release Solaris Nevada snv_60 X86 Copyright 2007 Sun Microsystems, Inc. All Rights Reserved. Use is subject to license terms. Assembled 12 March 2007 # # cd /var/crash/solaris # mdb -k 1 Loading modules: [ unix genunix specfs dtrace uppc pcplusmp scsi_vhci ufs ip hook neti sctp arp usba uhci qlc fctl nca lofs zfs random md cpc crypto fcip fcp logindmux ptm sppp emlxs ipc ] > ::status debugging crash dump vmcore.1 (64-bit) from solaris operating system: 5.11 snv_60 (i86pc) panic message: ZFS: I/O failure (write on off 0: zio fffec38cf340 [L0 packed nvlist] 4000L/600P DVA[0]=<0:160225800:600> DVA[1]=<0:9800:600> fletcher4 lzjb LE contiguous birth=192896 fill=1 cksum=6b28 dump content: kernel pages only > *panic_thread::findstack -v stack pointer for thread ff00025b2c80: ff00025b28f0 ff00025b29e0 panic+0x9c() ff00025b2a40 zio_done+0x17c(fffec38cf340) ff00025b2a60 zio_next_stage+0xb3(fffec38cf340) ff00025b2ab0 zio_wait_for_children+0x5d(fffec38cf340, 11, fffec38cf598) ff00025b2ad0 zio_wait_children_done+0x20(fffec38cf340) ff00025b2af0 zio_next_stage+0xb3(fffec38cf340) ff00025b2b40 zio_vdev_io_assess+0x129(fffec38cf340) ff00025b2b60 zio_next_stage+0xb3(fffec38cf340) ff00025b2bb0 vdev_mirror_io_done+0x2af(fffec38cf340) ff00025b2bd0 zio_vdev_io_done+0x26(fffec38cf340) ff00025b2c60 taskq_thread+0x1a7(fffec154f018) ff00025b2c70 thread_start+8() > ::cpuinfo -v ID ADDR FLG NRUN BSPL PRI RNRN KRNRN SWITCH THREAD PROC 0 fbc31f80 1b20 99 nono t-0ff00025b2c80 sched || RUNNING <--++--> PRI THREAD PROC READY60 ff00022c9c80 sched EXISTS60 ff00020e9c80 sched ENABLE ID ADDR FLG NRUN BSPL PRI RNRN KRNRN SWITCH THREAD PROC 1 fffec11ad000 1f30 59 yesno t-0fffec3dcbbc0 syslogd || RUNNING <--++--> PRI THREAD PROC READY60 ff000212bc80 sched QUIESCED59 fffec1e51360 syslogd EXISTS59 fffec1ec2180 syslogd ENABLE > ::quit This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
