Hi James, Thanks for the info. After having read about the tunable parameters my impression was that the default values were designed to work in most environments but in some specific environments they might not be optimal. My thinking with the ssd_max_throttle was that path failover time would be a little quicker if my host has to retry fewer commands so I was thinking that setting max_throttle to as low a value as possible without affecting I/O performance on my host would be desirable. Also, this would provide some protection to me against having a bunch of my hosts fill up the target port queue on my array.
The fp_offline_ticker, according to a doc I read about this stack, has a default value of 90 seconds. That seems a bit long for a small to medium 2Gb fabric, so I thought I might improve path failover here again. The ssd_io_parameter is 60 seconds by default. I don't think I have very many normal situations where I would reach this limit so I would just prefer to retry/failover sooner. I'm not certain I want to adjust the ssd_retry_count but I would like to be certain of the default behavior and since I get the error when I have ssd_retry_count in my system file I was concerned about what that parameter was really set to. In your reply, were you saying that I could use sd_* parameters instead of ssd_* parameters to adjust ssd throttles on sparc systems? Thanks again for the assistance. Regards, Vic This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
