Using 2008.11 and AVS I'm getting the following error when trying to run "sndradm -g primary -nu" on my primary server --
sndradm: warning: SNDR: Could not open file <slaveservername>:/dev/rdsk/c3t3d0s0 on remote node First of all, I've done this many times on 2008.05 without problem. Secondly, I understand the packaging problems with 2008.11 and AVS so I followed the steps recommended here - http://www.mail-archive.com/storage-disc...@opensolaris.org/msg05345.html, namely to install AVS like so: pkg install SUNWscm pkg install SUNWspsv pkg install SUNWrdc pkg install SUNWii Then I run dscfgadm, which works, but of course dscfgadm -i does not. The script has an error, so I followed the suggestion here - http://www.mail-archive.com/storage-disc...@opensolaris.org/msg04676.html, namely to modify the /usr/sbin/dscfgadm ksh script on line 1020 and change: typeset svc=$1 to typeset svc='$1' After all that, I get the following result from dscfgadm -i SERVICE STATE ENABLED nws_scm online true nws_sv online true nws_ii online true nws_rdc online true nws_rdcsyncd online true Availability Suite Configuration: Local configuration database: valid I ran an identical sndradm command on both the primary and the secondary (the same way I've done it in 2008.05) : sndradm -ne <primaryservername> /dev/rdsk/c3t3d0s0 /dev/rdsk/c3t3d0s1 <secondaryservername> /dev/rdsk/c3t3d0s0 /dev/rdsk/c3t3d0s1 ip sync g primary I also have both host names in /etc/hosts on both servers. So everything looks good, but I still get the "could not open file on remote node" error mentioned above. Lastly, for anyone wondering why I'm so interested in doing this on 2008.11, I can't use any other version for the following reasons -- 2008.05 - doesn't have the zfs_write_limit_override setting. Absolutely required in my scenario, otherwise ZFS batches up writes in a way that results in poor perceived performance of my application (stuttering). See: http://www.mail-archive.com/zfs-disc...@opensolaris.org/msg28704.html http://opensolaris.org/jive/thread.jspa?threadID=119421 http://www.mail-archive.com/zfs-disc...@opensolaris.org/msg26672.html. 2009.06 - hangs on large zfs send/recv jobs. I use daily snapshots, and when this doesn't work properly, I can't back up. See: https://opensolaris.org/jive/thread.jspa?messageID=384540 http://www.mail-archive.com/zfs-discuss at opensolaris dot org/msg34493.html http://www.mail-archive.com/zfs-discuss at opensolaris dot org/msg37158.html Build 134b - We're not NASA, but we're not in a van down by the river either. I know OpenSolaris is probably not considered production worthy for large corporations (they're supposed to get REAL Solaris or just play around with OpenSolaris I guess), probably in the same way that in the Linux world CentOS and Fedora aren't "production worthy" for the same type of organization, but it works fine for us. That being said, we're big enough to not feel comfortable using a development build for our server. Even if it's better/stabler/whatever than the other versions, it's a bit too unprofessional and I simply won't get away with it (especially if something went wrong - "What? It's a beta version?"). If Oracle won't call it a "release" for whatever reason, I can't use it like one. 2010.XX - Can't wait, I need to build a server sometime before the end of the Obama administration. So I'm pretty much forced into 2008.11. I hope I don't have to add 2008.11 to my list of versions I can't use, since there aren't any left! Thanks in advance for any suggestions! -- This message posted from opensolaris.org _______________________________________________ opensolaris-help mailing list opensolaris-help@opensolaris.org
