I am not sure what is happening at 1840. The current topology is royal (the machine in this backtrace) connected via 2 fibre channel connections directly to a Powervault 224F jbod. This is then connected via 2 connections again to another 224F, which is then connected to another machine, fiord (which also has had problems). I had royal connected to one 224f with 2 connections and did not connect that jbod to anything else, and it worked with no problems for the time it was connected like that (2 days). I have also tried connecting fiord and royal to two powervault 51f switches in a redundant configuration and then the switches to the 224Fs. This also generated problems and was where most of the backtraces in the bug reports came from. I have set qlport_down_retry=1 for faster failover. Should I unset it? A constant stream of RESETs is not expected. On Fri, Aug 7, 2009 at 3:01 AM, Andrew Vasquez<andrew.vasquez@xxxxxxxxxx> wrote: > Could you let me know what's going on at timestamp - 1840: > 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? -- 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
