Thanks very much! That was a really explanation about monitors, and i will bookmark that informations to start to implement it later. But, what do you think in save "that" information on the filesystem? The solution that i'm working on, is for "nonshared" storage, but the "issue" that i'm trying to solve is for the use with AVS. So, i can assume that the discs are in sync, the other way (without AVS), i don't have the problem at all. Sorry by the english, i hope you can understand... I mean, I'm just trying to know if i need to: - do a reverse sync (the pool was last loaded on secondary node) - don't need to do nothing (the pool was last loaded on primary node) It would be nice if i could put that information on the pool properties... but i think there is no "generic" property that i can use. So, i'm thinking in create a "little" filesystem on it, and handle that problem within. What do you think? ps.: The SC does not have that information? I can not know where the resource was last started using standard SC functions?
Leal. -- This message posted from opensolaris.org
