Karl Rossing wrote:
> Jim Dunham wrote:
>> Karl Rossing wrote:
>>> Jim Dunham wrote:
>>>>> I managed to get LDOMS setup on a T1000.
>>>>>
>>>>> The disk that i'm presenting to the secondary AVS ldom is an svm
>>>>> volume (/dev/md/dsk/d20). Inside the ldom, the disk(/dev/md/dsk/
>>>>> d20) looks like /dev/dsk/c0d2s0.
>>>>>
>>>>> The secondary volume is now being replicated for the 1st time.
>>>>> The command i used was sndradm -m secondary:/dev/rdsk/c0d2s0.
>>>>
>>>> What does your replicated configuration look like?
>>>>
>>>> The reason that I am asking is the a complete SNDR replica
>>>> consist of the follow components.
>>>>
>>>> primary host
>>>> primary device
>>>> primary bitmap
>>>> secondary host
>>>> secondary device
>>>> secondary bitmap
>>>> replication type (sync, or async)
>>>>
>>>> At enable time the command the must be invoked on both the
>>>> primary and secondary hosts, and looks something like this:
>>>>
>>>> sndradm -e <phost> <pdev> <pbmp> <shost> <sdev> <sbmp> ip {sync
>>>> | async} [g <group>] [q <qdev>]
>>>>
>>> sndradm -e primary /dev/rdsk/c0d1s0 /dev/rdsk/c0d2s0 secondary /
>>> dev/rdsk/c0d2s0 /dev/rdsk/c0d3s0 ip async
>>
>> So, what happens when you invoke this SNDR command, of course the
>> first one two times, once one "primary" and once on "secondary"?
>>
> No problems. Everything gets setup.
>
>>>
>>>
>>>> At update time
>>>>
>>>> sndradm -m shost:sdev
> This command dies after a while.
> sndradm: warning: SNDR: Dual copy failed, offset:10002432
>
> I'm going to try it with the database turned off on the primary and
> see if it gets farther.
>
> It made it to 80% but now it's stopping at 97%
>
> bash-3.00# dsstat
> name t s pct role ckps dkps tps svt
> dev/rdsk/c0d2s0 P L 97.62 net 0 0 0 0
> dev/rdsk/c0d2s0 bmp 0 0 0 0
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
Jim
>
>
>
>>> sndradm -m secondary:/dev/rdsk/c0d2s0
>> How about the update command, or the following?
>>
>> sndradm -P
>> sndradm -p
>> dsstat
> bash-3.00# sndradm -P
> /dev/rdsk/c0d1s0 -> wpg-srv3-ld2:/dev/rdsk/c0d2s0
> autosync: off, max q writes: 4096, max q fbas: 16384, async threads:
> 2, mode: async, state: logging
> bash-3.00# sndradm -p
> /dev/rdsk/c0d1s0 -> wpg-srv3-ld2:/dev/rdsk/c0d2s0
> bash-3.00# dsstat
> name t s pct role ckps dkps tps svt
> dev/rdsk/c0d2s0 P L 97.62 net 0 0 0 0
> dev/rdsk/c0d2s0 bmp 0 0 0 0
>
>
>
>
>
> 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.
Jim Dunham
Engineering Manager
Storage Platform Software Group
Sun Microsystems, Inc.
1617 Southwood Drive
Nashua, NH 03063
Tel..: 781.442.4042
Cell: 603.724.3792
Blog: http://blogs.sun.com/avs/
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
