[stgt] tgtd segfault with software RAID, hard resetting link

FUJITA Tomonori fujita.tomonori at lab.ntt.co.jp
Tue Apr 21 12:39:02 CEST 2009

On Tue, 21 Apr 2009 12:30:36 +0200
Tomasz Chmielewski <mangoo at wpkg.org> wrote:

> Tomasz Chmielewski schrieb:
> >> Tomasz, any chance to test the patch?
> > 
> > Now, tgtd survives 100 iterations here (with /dev/sdd being a part of 
> > software RAID-5 array):
> > 
> > i=1; while [ $i -ne 100 ] ; do hdparm -Y /dev/sdd;  i=$((i+1)); done
> > 
> > 
> > Previously, it would segfault after ~10 iterations.
> It segfaults elsewhere now ;)
> Doing "hdparm -Y /dev/sdd" in a loop so many times resulted in IO errors 
> on the initiator as a result of timeout values not high enough in 
> /sys/class/scsi*/*/device/timeout.
> So I rebooted the initiator without logging it out of the target, with 
> "echo b >/proc/sysrq-trigger" (it's a diskless initiator, so basically 
> that's the only method when its disks are gone).
> Initiator started to boot again and I think tgtd segfaulted when the 
> initiator tried to log in to the target.

Duh, seems that we have another problem.

Can you reproduce this by just rebooting the initiator without logging
out and starting the initiator again?
To unsubscribe from this list: send the line "unsubscribe stgt" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

More information about the stgt mailing list