[2.6.11-rc4-bk9] Bad behaviour using RAID

[Bill Davidsen]

I just added a few more 200GB drives on a Promise controller, and they 
are configured as:
  md0 - raid1, 6GB of stuff I really don't want to lose 64k stripe
  md1 - raid0, 350GB for streaming video capture, 512k stripe
This space was configured with "mdadm" if that makes a difference, and I 
didn't get the right options to make it start at boot, so it gets run 
out of rc.local. I doubt that makes a difference, but I mention it.

Since this machine is often idle for hours, I have the two drives of 
interest set to spin down after 20 minutes of disuse. Other than a 
fairly slow start I have had no problems with restarting after an idle 
period.

There are no problems with data corruption or error messages, nor have I 
ever see any indication of a rebuild in progress. HOWEVER, every once in 
a while the disk light comes on and the system becomes very 
unresponsive. Since the Promise controller isn't connected to the disk 
light, the activity is one the original (120gb, 200gb) drives somewhere. 
The system is unresponsive for 1-2 minutes, although not totally so, I 
can look at /proc/mdstat and see no rebuild, and even guess that the 
raid drives are spun down because access takes seconds after the system 
seems normal.

The system was up since the night the kernel was released, and I never 
saw any such behaviour until I added the other drives, but the activity 
is not on the new drives. This happens 1-2 times a day by observation, 
and since I use the system remotely during the week, I can only say that 
I haven't seen the unresponsive behaviour before, nor observed it on the 
weekend in the office. If I see it several times a day it's likely to be 
happening more often.

If anyone has even the slightest clue what's happening, I'd love to hear 
it. It started when the new hardware was added, but occurs on the old.

--
   -bill davidsen (davidsen@xxxxxxx)
"The secret to procrastination is to put things off until the
 last possible moment - but no longer"  -me
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/