From: NetComrade (netcomrade@bookexchange.net)
Date: Fri Nov 21 2003 - 09:08:39 EST
In the past we had issues when one disk would go out it would affect the
entire array (or loop, meaning multiple arrays). The good fix used to be
to make sure all revs were up to date. Not only that, but usually a bad
disk would cause IO problems like I am having after applying this patch.
Anyone seen this?
Should I downrev?
How is that done?
iostat xtcn shows service times and busy times way too high for this kind
of IO load:
18G drives: (rev: 0726->1126)
extended device statistics
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
6.2 8.6 24.8 37.7 0.0 0.4 0.0 26.0 0 24 c4t3d0
7.4 6.4 29.5 27.9 0.0 0.1 0.0 10.6 0 11 c4t5d0
7.0 4.8 31.1 20.7 0.0 0.2 0.0 17.7 0 17 c1t54d0
6.6 8.2 26.3 32.7 0.0 0.2 0.0 15.4 0 17 c1t57d0
4.8 6.2 19.1 26.3 0.0 0.2 0.0 21.3 0 16 c1t53d0
4.8 2.0 19.1 8.8 0.0 0.2 0.0 25.5 0 15 c1t50d0
4.0 14.3 18.3 60.6 0.0 0.3 0.0 16.2 0 16 c1t55d0
...
the 9G drives are doing a bit better (but seems like might be affected as
well) (rev: 1129->1229)
0.0 11.0 0.0 211.2 0.0 0.1 0.0 5.1 0 5 c4t100d0
0.0 17.0 0.0 210.2 0.0 0.1 0.0 4.8 0 7 c1t116d0
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:27:32 EDT