Simon Crosland wrote: > Karl, > > On Fri, Apr 4, 2008 at 9:21 PM, Karl Rossing <[EMAIL PROTECTED]> wrote: > >> primary:/var/adm/messages >> Apr 4 14:34:45 primary rdc: [ID 455011 kern.notice] NOTICE: SNDR: >> Interface 10.0.0.2 <==> 10.0.0.4 : Down >> Apr 4 14:34:57 primary rdc: [ID 942480 kern.warning] WARNING: >> rdc_sync_wrthr: remote write failed (67) 0x1106 >> Apr 4 14:34:57 primary last message repeated 3 times >> Apr 4 14:35:29 primary rdc: [ID 701429 kern.info] NOTICE: sndr: >> secondary:/dev/rdsk/c0d2s0 entered logging mode: sync failed to complete >> > > That's the primary seeing a network write failure which matches the > secondary. What happens just before this in primary:/var/adm/messages > ? > > If you run a ping -s concurrent with the sndradm -m does it show > network problems at about the same time that the resync dies? > yes. The network dies and comes backup eventually.
> Does the resync always die at the same offset does not appear to be so. Mar 14 17:19:37 librdc: SNDR: Dual copy failed, offset:15392512 Mar 14 17:19:38 sndr: SNDR: Dual copy failed, offset:15392512 Mar 18 14:09:07 librdc: SNDR: Dual copy failed, offset:9566208 Mar 18 14:09:08 sndr: SNDR: Dual copy failed, offset:9566208 Apr 01 10:37:44 librdc: SNDR: Dual copy failed, offset:82498560 Apr 01 10:37:45 sndr: SNDR: Dual copy failed, offset:82498560 Apr 01 11:01:21 librdc: SNDR: Dual copy failed, offset:8641280 Apr 01 11:01:22 sndr: SNDR: Dual copy failed, offset:8641280 Apr 01 11:19:17 librdc: SNDR: Dual copy failed, offset:10002432 Apr 01 11:19:18 sndr: SNDR: Dual copy failed, offset:10002432 Apr 04 14:11:57 librdc: SNDR: Dual copy failed, offset:9354240 Apr 04 14:11:58 sndr: SNDR: Dual copy failed, offset:9354240 Apr 04 14:35:29 librdc: SNDR: Dual copy failed, offset:10137088 Apr 04 14:35:30 sndr: SNDR: Dual copy failed, offset:10137088 CONFIDENTIALITY NOTICE: This communication (including all attachments) is confidential and is intended for the use of the named addressee(s) only and may contain information that is private, confidential, privileged, and exempt from disclosure under law. All rights to privilege are expressly claimed and reserved and are not waived. Any use, dissemination, distribution, copying or disclosure of this message and any attachments, in whole or in part, by anyone other than the intended recipient(s) is strictly prohibited. If you have received this communication in error, please notify the sender immediately, delete this communication from all data storage devices and destroy all hard copies. _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
