Karl, > primary:/var/adm/ds.log > Apr 04 14:26:13 sndr: sndradm -m primary /dev/rdsk/c0d1s0 /dev/rdsk/ > c0d2s0 secondary /dev/rdsk/c0d2s0 /dev/rdsk/c0d3s0 Sync Started > Apr 04 14:35:29 librdc: SNDR: Dual copy failed, offset:10137088 > Apr 04 14:35:30 sndr: SNDR: Dual copy failed, offset:10137088
On page 85/86 of the following troubleshooting guide we discuss the error above. http://docs.sun.com/app/docs/doc/819-6151-10?a=load It would be interesting to see if the block offset of 10137088 (or byte offset of 5190189056) has any special meaning to the secondary volume /dev/rdsk/c0d2s0 > > Apr 04 14:35:30 sndr: sndradm -m primary /dev/rdsk/c0d1s0 /dev/rdsk/ > c0d2s0 secondary /dev/rdsk/c0d2s0 /dev/rdsk/c0d3s0 > Sync Ended > > 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 The above error message is from here: http://cvs.opensolaris.org/source/xref/nwsc/src/sun_avs/uts/common/ns/rdc/rdc_io.c#2866 Looking deeper into the code: The remote (primary -> secondary) write failed with an error (67). From the file usr/src/uts/common/sys/errno.h #define ENOLINK 67 /* the link has been severed */ Since this replication link was stated as being loopback on the same host, and it failed or the link was severed, it would be interesting to find out what could cause that error. I think there are some Solaris TCP/IP counters, errors, etc., but I am not sure how these apply to single node testing between ldoms. The second value just indicates the current status of the SNDR replica. A 0x1106 is: #define RDC_ENABLED 0x2 /* RDC enabled */ #define RDC_PRIMARY 0x4 /* This node is the primary */ #define RDC_SYNCING 0x100 /* Synch in progress */ #define RDC_FULL 0x1000 /* Full sync, not an update */ > > 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 > > > secondary:/var/adm/ds.log > *nothing* > > secondary:/var/adm/messages > Apr 4 14:31:03 secondary xntpd[197]: [ID 774427 daemon.notice] time > reset (step) -0.185255 s > Apr 4 14:34:57 secondary rdc: [ID 455011 kern.notice] NOTICE: SNDR: > Interface 10.0.0.4 <==> 10.0.0.2 : Down > > > Jim Dunham wrote: >> >> On Apr 4, 2008, at 3:46 PM, Karl Rossing wrote: >> >>> Jim Dunham wrote: >>>> >>>> For SNDR to drop into logging mode, the "L", there must be some >>>> network connectivity or remote host issues. Take a look at the >>>> tail of /var/adm/messages, or /var/adm/ds.log >>>> >>> The interface is definitely going down. >>> >>> /var/adm/messages >>> Apr 4 14:34:57 secondary rdc: [ID 455011 kern.notice] NOTICE: >>> SNDR: Interface 10.0.0.4 <==> 10.0.0.2 : Down >> >> Any adjacent errors in the log file that seem relevant? >> Since this is a secondary host error, what happened at this >> timestamp on the primary? Look in both /var/adm/messages* and /var/ >> adm/ds.log >> >> Jim >> >> >>> >>> >>> Then the interface comes back up. >>> >>> Both primary and secondary AVS hosts are in an LDOM. They are also >>> using the same interface. >>> >>> There must be something in the Logical Domain Software that is >>> bringing down the virtual interface. >>> >>> >>> 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. >> > > > > 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
