Re: 'Device not ready' issue on mpt2sas since 3.1.10

2012-07-09 Thread Robert Trace
> I did some further research regarding my problem. > It appears to me the fault does not lie with the mpt2sas driver (not > that I can definitely exclude it), but with the md implementation. I'm actually discovering some of the same issues (LSI 9211-8i w/ SATA disks), but I've come to a slightly

Re: 'Device not ready' issue on mpt2sas since 3.1.10

2012-07-09 Thread Robert Trace
On 07/09/2012 04:45 PM, Darrick J. Wong wrote: > > I suspect that /sys/devices//manage_start_stop = 0 > for the SATA devices hanging off the SAS controller. Yep, looks like you're right. For my system: # cat /sys/block/sd?/device/scsi_disk/*/manage_start_stop 1 1 1 1 1 0 0 0 0 0 0 0 0 Those fir

Re: 'Device not ready' issue on mpt2sas since 3.1.10

2012-07-09 Thread Robert Trace
[removed linux-raid since the md layer seems unrelated] On 07/09/2012 08:12 PM, Matthias Prager wrote: >> >> I've reproduced this behavior on the raw disks themselves, no MD layer >> involved (although the freak-out by my MD layer is what alerted me to >> this issue too... Having your entire array

Re: 'Device not ready' issue on mpt2sas since 3.1.10

2012-07-09 Thread Robert Trace
On 07/09/2012 08:21 PM, Matthias Prager wrote: > > I haven't checked the scsi logging side, but about the only commands > that wake up the disks are 'smartctl -a /dev/sda' and 'sg_start' > (smartcl maybe issuing a START UNIT command on it's own). smartctl -a does appear to wake the disks. The scs

Re: 'Device not ready' issue on mpt2sas since 3.1.10

2012-07-10 Thread Robert Trace
On 07/09/2012 09:51 PM, Robert Trace wrote: > > Huh.. I just retested this and I'm seeing really random behavior. Ok, with a refined test I've been able to reliably reproduce this and I bisected it back to commit 85ef06d1d252f6a2e73b678591ab71caad4667bb in Linus' tree (i

Re: 'Device not ready' issue on mpt2sas since 3.1.10

2012-07-26 Thread Robert Trace
On 07/25/2012 07:56 PM, Matthias Prager wrote: > > I don't yet understand all the code but I'm following your discussion > with Tejun: I've set up a minimal vm running gentoo with a mpt2sas > driven controller in passthrough mode. I've applied your proposed patch > against the vanilla 3.5.0 kernel

Re: 'Device not ready' issue on mpt2sas since 3.1.10

2012-07-26 Thread Robert Trace
On 07/25/2012 06:35 PM, tomm wrote: > > If this is a driver or firmware bug, then why would commit > 85ef06d1d252f6a2e73b678591ab71caad4667bb > cause this to happen? What is the interaction between this issue > and this commit which just flushes events? That's confusing to me as well. Tejun's p

Re: 'Device not ready' issue on mpt2sas since 3.1.10

2012-08-16 Thread Robert Trace
On 07/25/2012 03:55 PM, James Bottomley wrote: > > Well, reading it, so do I. Unfortunately, we get to deal with the world > as it is rather than as we would wish it to be. We likely have this > problem with a lot of USB SATLs as well ... Has this patch made it into the main git trees yet? I h

Re: 'Device not ready' issue on mpt2sas since 3.1.10

2012-08-16 Thread Robert Trace
On 08/16/2012 04:24 PM, Matthias Prager wrote: > > Not yet, but it is in James scsi misc tree and last I heard was > scheduled for inclusion in the 3.6 kernel. Close enough. :-) I didn't track the changes on the SCSI tree and I just wanted to make sure that it didn't slip through the cracks. Th