That's the log message of my agent. Basically, in a switch back scenario it takes three actions: 1) /usr/sbin/sndradm -C local -g MYPOOL -n -u -r. 2) /usr/sbin/sndradm -C local -g MYPOOL -n -w. 3) Import the pool.
That's why i start this thread, because the agent always wait the completation of the reverse sync procedure, and after that it mounts the pool. So, i will look what you have told me, and create a extension to let administrators choose between "wait" or "mount" and get on-demand pull like you said. Now, for example, i did a "clnode evacuate" on my secondary node. The AVS software was in logging mode with "pct" 0.18 in both discs. Now after ten minutes, the dsstat command on primary node reports: name t s pct role ckps dkps tps svt dev/rdsk/c2d0s0 P RS 0.18 net - 0 0 0 dev/rdsk/c2d0s1 bmp 0 0 0 0 dev/rdsk/c3d0s0 P R 0.00 net - 0 0 0 dev/rdsk/c3d0s1 bmp 0 0 0 0 Why? The synchronization for the c3 disc was instantaneous, and the c2 is take so long... I did not realize why sometimes in replication mode (both discs), the pct number increase on primary node. A lot of questions, sorry. :) Leal. This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
