Session termination error incorrectly reported as cache coherency error
If a session is terminated, or gets a lostOT, while it is performing a page read, the page read is also terminated to avoid any risk of cache coherency problems. The failure of the page read was incorrectly being reported as a cache coherency error, rather than just reporting a warning. This cause of cache coherency errors does not indicate any problem with pages in the cache or on disk.
Workaround
If the session reporting a cache coherency error includes the message "IO error, page read failed", and was terminated or had a lostOT immediately prior, you can ignore this error. Note that if STN_HALT_ON_FATAL_ERR is set to true, this error can cause the stone to shut down.
Last updated: 6/26/08