Karl, > Good Day!
Good Evening! > > After getting some LDoms setup, I'm finally able to test out the AVS > compile i did against the Feb 19th AVS release on S10U4. > > I'm following the directions from > http://docs.sun.com/source/819-6148-10/index.html > > There doesn't seem to be exact steps in the docs on how to setup the > bitmap. The docs make mention of a memory bitmap. I think you may be a little confused. There is always a requirement for a bitmap volume, even if at times there is a portion of this bitmap in memory. The bitmap is a key element is ensuring that all changes (write I/Os), get replicated. > The docs make mention of > sndradm -e rmshost1 /dev/rdsk/c0t117d0s3 /dev/vx/rdsk/bmap/bm1 > \rmshost2 > /dev/rdsk/c0t117d0s5 /dev/vx/rdsk/bmap/bm2 ip async > > To use a memory bitmap to i simply run > sndradm -e rmshost1 /dev/rdsk/c0t117d0s3 \rmshost2 /dev/rdsk/ > c0t117d0s5 > ip async There is never the option to only run a memory based bitmap, as the bitmap is always backed up by a bitmap volume. > > > Karl > > PS: this might help too > bash-3.00# dsbitmap -r /dev/rdsk/c0d1s0 > Remote Mirror bitmap sizing > > Data volume (/dev/rdsk/c0d1s0) size: 419430400 blocks > Required bitmap volume size: > Sync replication: 1601 blocks > Async replication with memory queue: 1601 blocks > Async replication with disk queue: 14401 blocks > Async replication with disk queue and 32 bit refcount: 52801 blocks As you can see from the output of "dsbitmap", it mentions a "Required bitmap volume size:" I hope this helps. Chapter one of the following manual gives a Theory of Operations, which should help in understanding the importance of the bitmap volume. http://docs.sun.com/app/docs/doc/819-6148-10 - Jim > > > > > > 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 _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
