From: Bart V. A. <bva...@ac...> - 2014-08-26 13:00:47
|
On 08/26/14 13:31, Paul Fitzgibbons wrote: > I think I've posted a similar question to this in the past without > response. > > We are currently using the "stable" 2.2.x release but regularly get > into a condition where we have "stuck" threads which then requires a > SAN reboot. This is annoying because it then means we need to schedule > downtime to reboot the SANs (We are hosting LIVE website VMs on these). > Fortunately we can catch the condition by monitoring the load when the > stuck threads start to occur. > > I would be keen to know if anyone is using the 3.x branches in a LIVE > mission critical environment - can anybody please confirm if they are > doing this? Please do not hijack an existing e-mail thread but start a new thread if you want to discuss another topic. The code on the SCST 2.2.x branch is used in many live mission critical environments. So if your storage server is not working reliably there must be some aspect of that storage server that differs from what other SCST users are using. Bart. |