Try throttling back the max # of IOs. I saw a number of errors similar to
this on Pillar and EMC.
In /etc/system, set:
set sd:sd_max_throttle=20
and reboot.
I have added the setting and rebooted. I'm doing the same tests now
and will know in a day or so if I can avoid the error (from the
Try throttling back the max # of IOs. I saw a number of errors similar to this
on Pillar and EMC.
In /etc/system, set:
set sd:sd_max_throttle=20
and reboot.
I have added the setting and rebooted. I'm doing the same tests now
and will know in a day or so if I can avoid the error (from the
Try throttling back the max # of IOs. I saw a number of errors similar to this
on Pillar and EMC.
In /etc/system, set:
set sd:sd_max_throttle=20
and reboot.
This message posted from opensolaris.org
___
zfs-discuss mailing list
On HDS arrays we set sd_max_throttle to 8.
gino
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Gino Ruopolo wrote:
On HDS arrays we set sd_max_throttle to 8.
HDS provides an algorithm for estimating sd[d]_max_throttle in their
planning docs. It will vary based on a number of different parameters.
AFAIK, EMC just sets it to 20.
-- richard
___
The thought is to start throttling and possibly tune up or down, depending on
errors or lack of errors. I don't know of a specific NexSAN throttle preference
(we use SATABoy, and go with 20).
This message posted from opensolaris.org
___
zfs-discuss
JS wrote:
The thought is to start throttling and possibly tune up or down, depending
on errors or lack of errors. I don't know of a specific NexSAN throttle
preference (we use SATABoy, and go with 20).
One guess is as good as another :-) The default is 256, so even with 20
you are a long way
