On Thu, 06 Aug 2009, Thomas Georgiou wrote: > Here is a new log with error logging enabled: > http://www.tjhsst.edu/~2010tgeorgio/fclogs/dmesg4.log > > The enclosures do not have conflicting scsi ids. > Could you let me know what's going on at timestamp - 1840: [ 883.659657] bonnie++ used greatest stack depth: 3472 bytes left [ 1840.109135] scsi(1): Asynchronous LIP RESET (f8f7). [ 1840.109141] qla2xxx 0000:0a:01.0: LIP reset occurred (f8f7). [ 1840.109477] scsi(1): qla2x00_reset_marker() [ 1840.150025] scsi(1): fcport-0 - port retry count: 0 remaining [ 1840.150030] scsi(1): fcport-1 - port retry count: 0 remaining [ 1840.150034] scsi(1): fcport-2 - port retry count: 0 remaining [ 1840.150037] scsi(1): fcport-3 - port retry count: 0 remaining ... [ 1840.150113] scsi(1): fcport-26 - port retry count: 0 remaining [ 1840.150116] scsi(1): fcport-27 - port retry count: 0 remaining [ 1840.203564] scsi(1): LIP occurred (f7f7). [ 1840.203569] qla2xxx 0000:0a:01.0: LIP occurred (f7f7). [ 1840.234308] scsi(1): Asynchronous PORT UPDATE. [ 1840.234313] scsi(1): Port database changed b88f 0000 003f. [ 1841.100044] rport-1:0-0: blocked FC remote port time out: removing target and saving binding [ 1841.100101] qla2x00_mailbox_command(1): **** FAILED. mbx0=4006, mbx1=12, mbx2=ffff, cmd=71 **** [ 1841.100107] qla2x00_fabric_logout(1): failed=102 mbx1=12. there's seems to be a great deal of fabric disruptions occuring on the fibre. This seems to be occurring on both 22xx ports. It also appears that you've set port-down-timeout (dev-loss-tmo) to 0 seconds (for faster failovers)? Could you describe the topology? Would it be possible to isolate the faults, I take it the constant stream of RESETs are not expected? -- av -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
