Thomas H Jones II wrote:
> Ok, just wanted a sanity check, here. That is to say, find out if anyone
> else has experienced this issue.
>
> Any way, at my environment, we have a number of different clustered systems.
> Partners in each cluster are identically configured (same hardware and same
> OS and patches). However, we do run several different versions of VCS and
> Sun Cluster.
>
> Ocasionally, if a node is really busy and panics, when the filesystem gets
> re-assembled on the standby node, the fsck sometimes results in some of the
> active/open files disappearing into the ether.

Thinking from the Sun Cluster side, and I'm sure VCS too, no amount of
regular system "busy-ness" should result in a cluster failover and panic.
Unless, that is, your service monitors include a recipe for system being
busy and deem that as a reason to failover (which should still be elegant
without damaging filesystems).

So if you're really witnessing unexplained "busy leads to panic/failover"
get in contact with SunService for someone to investigate.

Gavin

> Anyone ever witnessed this? Is there any documentation out there on this
> subject (tried Googling, but nothing useful/recent turned up).
>
> -tom
>