<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Solaris-Express on sigtar.com</title>
		<link>https://sigtar.com/categories/solaris-express/</link>
		<description>Recent content in Solaris-Express on sigtar.com</description>
		<generator>Hugo</generator>
		<language>en-nz</language>
		
		
		
		
			<lastBuildDate>Thu, 11 Jul 2013 00:00:00 +1200</lastBuildDate>
		
			<atom:link href="https://sigtar.com/categories/solaris-express/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>nsswitch.conf SMF config</title>
				<link>https://sigtar.com/2013/07/11/nsswitch-conf-smf-config/</link>
				<pubDate>Thu, 11 Jul 2013 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2013/07/11/nsswitch-conf-smf-config/</guid>
				<description>&lt;p&gt;# svccfg svc:&amp;gt; select dns/client svc:/network/dns/client&amp;gt; setprop config/search = astring: \ (&amp;ldquo;us.company.com&amp;rdquo; &amp;ldquo;eu.company.com&amp;rdquo; &amp;ldquo;companya.com&amp;rdquo; &amp;ldquo;companyb.com&amp;rdquo; &amp;ldquo;company.com&amp;rdquo; ) svc:/network/dns/client&amp;gt; setprop config/nameserver = net_address: \ ( 138.2.202.15 138.2.202.25 ) svc:/network/dns/client&amp;gt; select dns/client:default svc:/network/dns/client:default&amp;gt; refresh svc:/network/dns/client:default&amp;gt; validate svc:/network/dns/client:default&amp;gt; select name-service/switch svc:/system/name-service/switch&amp;gt; setprop config/host = astring: &amp;ldquo;files dns&amp;rdquo; svc:/system/name-service/switch&amp;gt; select system/name-service/switch:default svc:/system/name-service/switch:default&amp;gt; refresh svc:/system/name-service/switch:default&amp;gt; validate svc:/system/name-service/switch:default&amp;gt; # svcadm enable dns/client # svcadm refresh name-service/switch # grep host /etc/nsswitch.conf hosts: files dns # cat /etc/resolv.conf # # opyright (c) 2011, Oracle and/or its affiliates. All rights reserved. #&lt;/p&gt;</description>
			</item>
			<item>
				<title>zfs share for Time machine backups</title>
				<link>https://sigtar.com/2013/07/11/zfs-share-for-time-machine-backups/</link>
				<pubDate>Thu, 11 Jul 2013 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2013/07/11/zfs-share-for-time-machine-backups/</guid>
				<description>&lt;p&gt;I&amp;rsquo;ve tried using a share for time machine before, but due to the nature of how time machine works it eventually consumed all the spare space that is available on that particular share.&lt;/p&gt;&#xA;&lt;p&gt;bring on zfs quotas&amp;hellip; (my drive on my mini mac is 100GB, so 200GB should be enough for a few variations)&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;zfs set quota=200G unprotected/timemachine&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;This adds a artificial limit to your zfs filesystem, making sure that time machine does not consume more than 200 gigabytes of space.&lt;/p&gt;</description>
			</item>
			<item>
				<title>opensolaris - setting up dhcp</title>
				<link>https://sigtar.com/2012/10/16/opensolaris-setting-up-dhcp/</link>
				<pubDate>Tue, 16 Oct 2012 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2012/10/16/opensolaris-setting-up-dhcp/</guid>
				<description>&lt;p&gt;You&amp;rsquo;ll need these two packages installed;&lt;/p&gt;&#xA;&lt;p&gt;SUNWdhcs, SUNWdhcm&lt;/p&gt;&#xA;&lt;p&gt;First ensure that the DHCP service is running. Go into the &amp;ldquo;services&amp;rdquo; gui and tick the box to enable the DHCP server.&lt;/p&gt;&#xA;&lt;p&gt;now from commandline run&amp;hellip;&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;dhcpmgr&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;ol&gt;&#xA;&lt;li&gt;From edit menu choose &amp;ldquo;network wizard&amp;rdquo;, step through the wizard (defautls are o.k i you have a fixed IP already assigned to your opensolaris box)&lt;/li&gt;&#xA;&lt;li&gt;From edit menu choose &amp;ldquo;address wizard&amp;rdquo;&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;If you step through the wizard (the following is an example of what i have choosen)&lt;/p&gt;</description>
			</item>
			<item>
				<title>solaris - storage server</title>
				<link>https://sigtar.com/2011/07/11/solaris-storage-server/</link>
				<pubDate>Mon, 11 Jul 2011 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2011/07/11/solaris-storage-server/</guid>
				<description>&lt;p&gt;&lt;a href=&#34;http://p2v.it/2010/04/15/a-next-generation-multiprotocol-storage-for-your-homelab-on-a-budget-part-1/&#34;&gt;http://p2v.it/2010/04/15/a-next-generation-multiprotocol-storage-for-your-homelab-on-a-budget-part-1/&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Setup iSCSI target using comstar &amp;ndash; &lt;strong&gt;pkg install -v storage-server pkg install pkg:/SUNWiscsit svcadm enable stmf svcadm enable svc:/network/iscsi/target:default itadm create-target&lt;/strong&gt; &lt;strong&gt;reboot &amp;ndash; -r&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Create the iSCSI store &amp;mdash; &lt;strong&gt;zfs create -V 100G DataPool/TestDatastore1 sbdadm create-lu /dev/zvol/rdsk/DataPool/TestDatastore1 stmfadm create-hg ESX4-group stmfadm add-hg-member -g ESX4-group wwn.2100001b329711bd wwn.2101001b32b711bd stmfadm add-view -h ESX4-group -n 0 600144F03EBEC50000004BA86E460001 stmfadm list-lu -v&lt;/strong&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>install crashplan on solaris</title>
				<link>https://sigtar.com/2011/06/11/install-crashplan-on-solaris-express/</link>
				<pubDate>Sat, 11 Jun 2011 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2011/06/11/install-crashplan-on-solaris-express/</guid>
				<description>&lt;p&gt;&lt;a href=&#34;http://support.crashplan.com/doku.php/getting_started/installing_crashplan&#34;&gt;http://support.crashplan.com/doku.php/getting_started/installing_crashplan&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Move the downloaded tar.gz file into /var/spool/pkg/&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;mv CrashPlan_2010-03-08_Solaris.tar.gz /var/spool/pkg/&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Unpack the archive.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;tar -xzvf CrashPlan_2010-03-08_Solaris.tar.gz&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Install the CrashPlan package:&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;sudo /usr/sbin/pkgadd&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Start CrashPlan Engine:&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;sudo /opt/sfw/crashplan/bin/CrashPlanEngine start&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Start CrashPlan Desktop:&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;sudo /opt/sfw/crashplan/bin/CrashPlanDesktop&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;To enable CrashPlan PRO as a service (as root):&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;svccfg import /opt/sfw/crashplan/bin/crashplan.xml&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;svcadm enable crashplan&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;check that the service has come online proplery (then load client)&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;svcs -a | grep crashplan&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;online         21:18:43 svc:/crashplan:default&lt;/em&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>email alerts on zpool failure</title>
				<link>https://sigtar.com/2011/06/02/1360/</link>
				<pubDate>Thu, 02 Jun 2011 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2011/06/02/1360/</guid>
				<description>&lt;p&gt;simple but functional script to check if your zpools are healthy and send email if they are not&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://blog.qcnetwork.com/2011/03/monitoring-zpool-with-email-alert.html&#34;&gt;http://blog.qcnetwork.com/2011/03/monitoring-zpool-with-email-alert.html&lt;/a&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>zfs : accidentally adding cache drive to raidz zpool</title>
				<link>https://sigtar.com/2011/05/04/zfs-accidentally-adding-cache-drive-to-raidz-zpool/</link>
				<pubDate>Wed, 04 May 2011 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2011/05/04/zfs-accidentally-adding-cache-drive-to-raidz-zpool/</guid>
				<description>&lt;p&gt;&lt;a href=&#34;http://forums.freebsd.org/showthread.php?t=23127&#34;&gt;http://forums.freebsd.org/showthread.php?t=23127&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Unfortunately if you have accidentally added a single drive into your raidz pool at the top-level there is no way to just remove the non redundant disk. Your pool is now &lt;strong&gt;dependant&lt;/strong&gt; on this disk.&lt;/p&gt;&#xA;&lt;p&gt;If you want your pool to be just raidz vdevs, then you will need to backup your data, destroy your pool, create a new pool, and restore your data.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;There is no current way to remove a top-level vdev from a pool.&lt;/strong&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>opensolaris - check syslog</title>
				<link>https://sigtar.com/2011/01/30/opensolaris-check-syslog/</link>
				<pubDate>Sun, 30 Jan 2011 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2011/01/30/opensolaris-check-syslog/</guid>
				<description>&lt;p&gt;&lt;strong&gt;dmesg | tail&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Shows the last few entries in the system log.&lt;/p&gt;</description>
			</item>
			<item>
				<title>OpenSolaris is Dead</title>
				<link>https://sigtar.com/2010/10/31/opensolaris-is-dead/</link>
				<pubDate>Sun, 31 Oct 2010 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2010/10/31/opensolaris-is-dead/</guid>
				<description>&lt;p&gt;&lt;a href=&#34;http://sstallion.blogspot.com/2010/08/opensolaris-is-dead.html&#34;&gt;http://sstallion.blogspot.com/2010/08/opensolaris-is-dead.html&lt;/a&gt;&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;OpenSolaris is Dead.&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;What follows is an email sent internally to Oracle Solaris Engineers which describes Oracle&amp;rsquo;s true intentions toward the OpenSolaris project and the future of Oracle Solaris.&lt;/p&gt;&#xA;&lt;p&gt;This concludes over four years that I (and many other external contributors) have worked on the OpenSolaris project. This is a terrible sendoff for countless hours of work - for quality software which will now ship as an Oracle product that we (the original authors) can no longer obtain on an unrestricted basis.&lt;/p&gt;&#xA;&lt;p&gt;I can only maintain that the software we worked on was for the betterment of all, not for any one company&amp;rsquo;s bottom line. This is truly a perversion of the open source spirit.&lt;/p&gt;&#xA;&lt;/blockquote&gt;</description>
			</item>
			<item>
				<title>opensolaris - increase swap</title>
				<link>https://sigtar.com/2010/07/26/opensolaris-increase-swap/</link>
				<pubDate>Mon, 26 Jul 2010 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2010/07/26/opensolaris-increase-swap/</guid>
				<description>&lt;p&gt;I found this on opensolaris forums&amp;hellip;. A nice way to increase your swap without the need for a reboot.&lt;/p&gt;&#xA;&lt;p&gt;First check your current swap size and details;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;swap -lh&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;or&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;zfs list&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Then create a temp swap zfs store and delete and increase swap&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;zfs create -V &lt;old size&gt; rpool/swp&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;swap -a /dev/zvol/dsk/rpool/swp&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;swap -d /dev/zvol/dsk/rpool/swap&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;zfs destroy rpool/swap&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;zfs create -V &lt;new size&gt; rpool/swap&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;swap -a /dev/zvol/dsk/rpool/swap&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;swap -d /dev/zvol/dsk/rpool/swp&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;zfs destroy rpool/swp&lt;/strong&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>OpenSolaris on HP server</title>
				<link>https://sigtar.com/2010/07/24/opensolaris-on-hp-server/</link>
				<pubDate>Sat, 24 Jul 2010 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2010/07/24/opensolaris-on-hp-server/</guid>
				<description>&lt;p&gt;A nice easy post by Evgeniy on getting opensolaris on HP kit&amp;hellip;.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://www.eject.name/2009/07/opensolaris-and-hp-smartarray.html&#34;&gt;http://www.eject.name/2009/07/opensolaris-and-hp-smartarray.html&lt;/a&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>4k sector hard drives and zfs</title>
				<link>https://sigtar.com/2010/06/06/4k-sector-hard-drives-and-zfs/</link>
				<pubDate>Sun, 06 Jun 2010 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2010/06/06/4k-sector-hard-drives-and-zfs/</guid>
				<description>&lt;p&gt;I hit this as a problem recently. One of my disks died in my raidz so i ran down to the store and grabbed me a replacement WD10EARS (Western Digital 1Tb Green) drive.&lt;/p&gt;&#xA;&lt;p&gt;BUT&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;The one thing the store didn&amp;rsquo;t mention to me is the new 4K cluster sizing on the drive. I guess they assume most people run windows (though the issues are also present in XP). See these posts&amp;hellip;&lt;/p&gt;</description>
			</item>
			<item>
				<title>opensolaris - pkg verify</title>
				<link>https://sigtar.com/2010/05/23/opensolaris-pkg-verify/</link>
				<pubDate>Sun, 23 May 2010 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2010/05/23/opensolaris-pkg-verify/</guid>
				<description>&lt;p&gt;I ran through a &lt;strong&gt;pkg verify&lt;/strong&gt; the other day and came across a lot of errors. Running the subsequent &lt;strong&gt;pkg fix&lt;/strong&gt; command presented me with this&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;pkg: Requested &amp;ldquo;install&amp;rdquo; operation would affect files that cannot be modified in live image.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;Please retry this operation on an alternate boot environment.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;This is the fix&amp;hellip;.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;mkdir /mnt/osol-134fix beadm create osol-134fix beadm mount osol-134fix /mnt/osol-134fix pkg -R /mnt/osol-134fix fix &amp;ndash;accept beadm activate osol-134fix&lt;/strong&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>opensolaris - default route</title>
				<link>https://sigtar.com/2010/05/11/opensolaris-default-route/</link>
				<pubDate>Tue, 11 May 2010 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2010/05/11/opensolaris-default-route/</guid>
				<description>&lt;p&gt;type the following to check your default routes&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;netstat -rn&lt;/strong&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>opensolaris v134 - CIFS has gone walkies</title>
				<link>https://sigtar.com/2010/04/11/opensolaris-v134-cifs-has-gone-walkies/</link>
				<pubDate>Sun, 11 Apr 2010 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2010/04/11/opensolaris-v134-cifs-has-gone-walkies/</guid>
				<description>&lt;p&gt;Errr, I cant find the CIFS service in the 134 build.&lt;/p&gt;&#xA;&lt;p&gt;I know it was renamed to as per below but still cant see it anywhere?&lt;/p&gt;&#xA;&lt;p&gt;&amp;gt; system/file-system/smb (was SUNWsmbfs*) &amp;gt; service/file-system/smb (was SUNWsmbs*)&lt;/p&gt;&#xA;&lt;p&gt;Anyone have any ideas?&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;pkg search *smb&lt;/strong&gt; gets me these&amp;hellip; but i cant install them.&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;require depend &lt;a href=&#34;mailto:service/file-system/smb@0.5.11-0.134&#34;&gt;service/file-system/smb@0.5.11-0.134&lt;/a&gt; pkg:/redistributable@0.1-0.134 require depend &lt;a href=&#34;mailto:service/file-system/smb@0.5.11-0.134&#34;&gt;service/file-system/smb@0.5.11-0.134&lt;/a&gt; pkg:/storage/storage-server@0.1-0.134 require depend &lt;a href=&#34;mailto:service/file-system/smb@0.5.11-0.134&#34;&gt;service/file-system/smb@0.5.11-0.134&lt;/a&gt; pkg:/system/security/kerberos-5@0.5.11-0.134 require depend &lt;a href=&#34;mailto:service/file-system/smb@0.5.11-0.134&#34;&gt;service/file-system/smb@0.5.11-0.134&lt;/a&gt; pkg:/storage/storage-nas@0.1-0.134 require depend &lt;a href=&#34;mailto:system/file-system/smb@0.5.11-0.134&#34;&gt;system/file-system/smb@0.5.11-0.134&lt;/a&gt; pkg:/redistributable@0.1-0.134 require depend &lt;a href=&#34;mailto:system/file-system/smb@0.5.11-0.134&#34;&gt;system/file-system/smb@0.5.11-0.134&lt;/a&gt; pkg:/storage/storage-server@0.1-0.134 require depend &lt;a href=&#34;mailto:system/file-system/smb@0.5.11-0.134&#34;&gt;system/file-system/smb@0.5.11-0.134&lt;/a&gt; pkg:/slim_install@0.1-0.134&lt;/em&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>zfs - now has dedup!</title>
				<link>https://sigtar.com/2010/04/05/zfs-now-has-dedup/</link>
				<pubDate>Mon, 05 Apr 2010 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2010/04/05/zfs-now-has-dedup/</guid>
				<description>&lt;p&gt;Cool. zfs as of version 21 has deduplication built in. And thats the good dedup - synchronous dedup. i.e. deduped on the fly!&lt;/p&gt;&#xA;&lt;p&gt;How easy is it to turn on? - very!&lt;/p&gt;&#xA;&lt;p&gt;Once you have upgraded your zpool to 21 or above you can run the following command at the pool level and deduplication will be over all your data from that point onwards.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;zpool set dedup=on tank&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Done&lt;/p&gt;&#xA;&lt;p&gt;Note : Watch your performance, it will drop like a rock if you do not have enough ram for your dedup tables. Do some tests after enabling this feature.&lt;/p&gt;</description>
			</item>
			<item>
				<title>OpenSolaris - iSCSI</title>
				<link>https://sigtar.com/2009/11/13/iscsi-in-opensolaris/</link>
				<pubDate>Fri, 13 Nov 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/11/13/iscsi-in-opensolaris/</guid>
				<description>&lt;p&gt;Want iSCSI in opensolaris?&lt;/p&gt;&#xA;&lt;p&gt;Grab SUNWiscsitgt via package manager.&lt;/p&gt;&#xA;&lt;p&gt;enable the server via svcadm;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;svcadm enable iscsitgt&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;create your zfs iscsi pool;  (this command will limit iscsi drive to 500GB in size)&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;zfs create -V 500G tank/iscsi&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;set isci on via zfs command;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;zfs set shareiscsi=on tank/iscsi&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;check that target is up and running;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;iscsitadm list target -v&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Done. Should be able to connect via ip from another machine. I have not covered CHAP or any client side configuration. Assumed isolated LAN.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Opensolaris - ZFS recovery after kernel panic</title>
				<link>https://sigtar.com/2009/10/19/opensolaris-zfs-recovery-after-kernel-panic/</link>
				<pubDate>Mon, 19 Oct 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/10/19/opensolaris-zfs-recovery-after-kernel-panic/</guid>
				<description>&lt;p&gt;Recently i hit what i thought was a huge disaster with my ZFS array. Essentially i was unable to import my zpool without causing the kernel to panic and reboot. Still unsure of the exact reason, but it didn&amp;rsquo;t seem to be due to a hardware fault. (zpool import showed all disks as ONLINE)&lt;/p&gt;&#xA;&lt;p&gt;When i tried to import with &lt;strong&gt;zpool import -f tank&lt;/strong&gt; the machine would lockup and reboot (panic).&lt;/p&gt;</description>
			</item>
			<item>
				<title>Opensolaris - white screen on logon</title>
				<link>https://sigtar.com/2009/10/08/opensolaris-white-screen-on-logon/</link>
				<pubDate>Thu, 08 Oct 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/10/08/opensolaris-white-screen-on-logon/</guid>
				<description>&lt;p&gt;I had this problem when i enabled 3d effects on my server. The screen just goes white and you cannot see anything. Even after a reboot as soon as you logon to gnome the screen goes white.&lt;/p&gt;&#xA;&lt;p&gt;To fix you&amp;rsquo;ll need to logon using a &amp;ldquo;failsafe terminal&amp;rdquo; session, then run &lt;strong&gt;gnome-cleanup&lt;/strong&gt; from the command line. This will blow away any of your gnome settings (although they are actually backed up to a file), but it&amp;rsquo;ll mean you&amp;rsquo;ll be able to logon again without issue.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Opensolaris - Samba and Network browsing</title>
				<link>https://sigtar.com/2009/09/06/opensolaris-samba-and-network-browsing/</link>
				<pubDate>Sun, 06 Sep 2009 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2009/09/06/opensolaris-samba-and-network-browsing/</guid>
				<description>&lt;p&gt;If you&amp;rsquo;ve setup samba (rather than the builtin cifs/smb) chances are that you can only browse to your samba shares directly on IP only.&lt;/p&gt;&#xA;&lt;p&gt;If you want your box &amp;ldquo;network browseable&amp;rdquo; you&amp;rsquo;ll need to load nmbd.&lt;/p&gt;&#xA;&lt;p&gt;You can find a really good write up on modifiying the SMF for samba to autostart the required service here : &lt;a href=&#34;http://wikis.sun.com/display/BigAdmin/Enabling+Browsing+with+Samba+in+Solaris+10+Update+4&#34;&gt;http://wikis.sun.com/display/BigAdmin/Enabling+Browsing+with+Samba+in+Solaris+10+Update+4&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;import this file &lt;a href=&#34;https://sigtar.com/wp-content/uploads/2009/09/samba.xml&#34;&gt;samba.xml&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;run these commands;&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;# svcadm disable samba&#xA;# svccfg import samba.xml&#xA;# svccfg delete svc:/network/samba:default&#xA;# svcadm refresh samba:smbd&#xA;# svcadm refresh samba:nmbd&#xA;# svcadm enable samba:smbd&#xA;# svcadm enable samba:nmbd&#xA;&lt;/code&gt;&lt;/pre&gt;</description>
			</item>
			<item>
				<title>VirtualBox - crashing / freezing</title>
				<link>https://sigtar.com/2009/09/05/virtualbox-crashing-freezing/</link>
				<pubDate>Sat, 05 Sep 2009 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2009/09/05/virtualbox-crashing-freezing/</guid>
				<description>&lt;p&gt;I&amp;rsquo;ve had some problems since my upgrade to virtualbox 2.2.0 on OpenSolaris. After some time all of my linux boxes seem to just die. The virtual machine just stops responding. Strangely there was no problem with my windows vms after the update.&lt;/p&gt;&#xA;&lt;p&gt;From what i can tell it looks like the upgrade turned off &amp;ldquo;&lt;strong&gt;IO APIC&lt;/strong&gt;&amp;rdquo; - this is the bit that seemed to cause the problem. Re-enabling this on all of my linux boxes seems to have fixed the problem. I&amp;rsquo;ll continue testing for another week and update this post if any problems re-occur.&lt;/p&gt;</description>
			</item>
			<item>
				<title>opensolaris - zfs PCI-e sata controller</title>
				<link>https://sigtar.com/2009/09/01/opensolaris-zfs-pci-e-sata-controller/</link>
				<pubDate>Tue, 01 Sep 2009 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2009/09/01/opensolaris-zfs-pci-e-sata-controller/</guid>
				<description>&lt;p&gt;Time for me to add some more sata ports to my opensolaris build. I&amp;rsquo;ve been using the &lt;a href=&#34;https://sigtar.com/2009/05/20/flashing-si3114-to-sata-only-bios/&#34;&gt;SI 3114 PCI&lt;/a&gt; cards  (4x sata) up until now without any issue, but they are limited by the bandwidth on the PCI slot. Time to upgrade and boost my performance.&lt;/p&gt;&#xA;&lt;p&gt;At the moment i&amp;rsquo;m looking at grabbing one of these UIO cards;&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://sigtar.com/wp-content/uploads/2009/07/AOC-USAS-L8i.gif&#34;&gt;&lt;img src=&#34;https://sigtar.com/wp-content/uploads/2009/07/AOC-USAS-L8i.gif&#34; alt=&#34;AOC-USAS-L8i&#34; title=&#34;AOC-USAS-L8i&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://www.supermicro.com/products/accessories/addon/AOC-USAS-L8i.cfm&#34;&gt;http://www.supermicro.com/products/accessories/addon/AOC-USAS-L8i.cfm&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;From what iv&amp;rsquo;e been reading these cards will work fine in a PCI-e slot (8x / 16x) after a bit of modding and display the drives straight to opensolaris without any additional drivers etc. (same chipset used in various sun servers)&lt;/p&gt;</description>
			</item>
			<item>
				<title>OpenSolaris - Samba server</title>
				<link>https://sigtar.com/2009/08/08/opensolaris-samba-server/</link>
				<pubDate>Sat, 08 Aug 2009 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2009/08/08/opensolaris-samba-server/</guid>
				<description>&lt;p&gt;Time to share your newly created ZFS volume via samba to your windows clients.  There is some CIFS / SMB support built into the kernel now, but i&amp;rsquo;ve grown used to the SMB server&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;Fire up add software - click filesystems - enable filter for &amp;ldquo;smb&amp;rdquo;, there are three packages generally. I get all three, but you only need the kernel update and the server package. The other is the SMB client.&lt;/p&gt;</description>
			</item>
			<item>
				<title>opensolaris - network teaming</title>
				<link>https://sigtar.com/2009/08/03/opensolaris-network-teaming/</link>
				<pubDate>Mon, 03 Aug 2009 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2009/08/03/opensolaris-network-teaming/</guid>
				<description>&lt;p&gt;Otherwise known as trunking or link aggregation. I believe it is the best way to get that additional boost out of your network server while providing a bit of redundancy on link failure. here is how to do it&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;Official docs on the process here&amp;hellip; &lt;a href=&#34;http://docs.sun.com/app/docs/doc/819-6990/gdysn?a=view&#34;&gt;http://docs.sun.com/app/docs/doc/819-6990/gdysn?a=view&lt;/a&gt; and some good bits here &lt;a href=&#34;http://blogs.sun.com/nickyv/entry/link_aggregation_jumpstart_post_install&#34;&gt;http://blogs.sun.com/nickyv/entry/link_aggregation_jumpstart_post_install&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;dladm&lt;/strong&gt; (data link admin) is the tool for the job. List the links you currently have&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;dladm show-link&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;First shut down the links you are currently using..  (you will have to do this on the console)&lt;/p&gt;</description>
			</item>
			<item>
				<title>opensolaris - smbd issues?</title>
				<link>https://sigtar.com/2009/07/27/opensolaris-smbd-issues/</link>
				<pubDate>Mon, 27 Jul 2009 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2009/07/27/opensolaris-smbd-issues/</guid>
				<description>&lt;p&gt;Hmm&amp;hellip; i&amp;rsquo;ve been having problems since the 2009.06 (snv_111b) update with cifs.&lt;/p&gt;&#xA;&lt;p&gt;Cant pin it exactly as it could be &amp;ldquo;load&amp;rdquo; related&amp;hellip; hmmm.&lt;/p&gt;&#xA;&lt;p&gt;found this ? &lt;a href=&#34;http://opensolaris.org/jive/thread.jspa?threadID=107681&#34;&gt;http://opensolaris.org/jive/thread.jspa?threadID=107681&lt;/a&gt; this also may be a clue.. &lt;a href=&#34;http://opensolaris.org/jive/thread.jspa?threadID=92472&amp;amp;tstart=75&#34;&gt;http://opensolaris.org/jive/thread.jspa?threadID=92472&amp;amp;tstart=75&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;imapd ?  might have to go back to 2008.11&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;You might get better performance if you enable oplocks but there are known issues with it but you can do it just to see if you see any difference:&lt;/p&gt;&#xA;&lt;p&gt;svccfg -s smb/server setprop smbd/oplock_enable=boolean: true&lt;/p&gt;&#xA;&lt;/blockquote&gt;</description>
			</item>
			<item>
				<title>OpenSolaris - Headless server</title>
				<link>https://sigtar.com/2009/07/26/opensolaris-headless-server/</link>
				<pubDate>Sun, 26 Jul 2009 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2009/07/26/opensolaris-headless-server/</guid>
				<description>&lt;p&gt;I&amp;rsquo;ve moved from a CentOS linux distro running vmware server 2.0 to OpenSolaris running VirtualBox. My previous system was totally headless and i wanted something similar to replace it.&lt;/p&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve just started getting into OpenSolaris for many reasons (Sun has some cool stuff - ZFS / VirtualBox). But I have always wanted to run OpenSolaris as a &lt;strong&gt;headless&lt;/strong&gt; server, and from what i initially found VirtualBox didn&amp;rsquo;t have the easy to use autostart on boot features that vmware server had. But there are always ways to get things working&amp;hellip;&lt;/p&gt;</description>
			</item>
			<item>
				<title>Opensolaris : Citrix XenServer / ESX - Hooking into ZFS</title>
				<link>https://sigtar.com/2009/07/22/citrix-xenserver-esx-hooking-into-zfs/</link>
				<pubDate>Wed, 22 Jul 2009 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2009/07/22/citrix-xenserver-esx-hooking-into-zfs/</guid>
				<description>&lt;p&gt;To share your zfs pool via NFS (that works with Citrix Xen / ESX) to a host called &amp;ldquo;esxhost&amp;rdquo;;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;zfs set sharenfs=rw,nosuid,root=esxhost tank/nfs&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Note : You MUST have a resolvable name from the opensolaris box. i.e. you should be able to ping it. I have tried with ip&amp;rsquo;s only and it will fail. I have edited the &lt;strong&gt;/etc/hosts&lt;/strong&gt; file to include the following line for my config;&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;# Copyright 2007 Sun Microsystems, Inc. All rights reserved. # Use is subject to license terms. # # ident &amp;ldquo;%Z%%M% %I% %E% SMI&amp;rdquo; # # Internet host table # 192.168.9.120 esxhost&lt;/em&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>opensolaris / zfs - whitebox build</title>
				<link>https://sigtar.com/2009/07/19/opensolaris-zfs-whitebox-build/</link>
				<pubDate>Sun, 19 Jul 2009 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2009/07/19/opensolaris-zfs-whitebox-build/</guid>
				<description>&lt;p&gt;I&amp;rsquo;ve built a little server for home use, but it pales in comparison to this beast&amp;hellip; This type of setup would be perfect for a lab / test environment that requires lots of fast and reliable disk. SCSI drives are fading out, SATA can perform if its setup right. When you look at the price of the entire build you wonder why corporations continue to spend the big bucks on the big storage names.&lt;/p&gt;</description>
			</item>
			<item>
				<title>zfs - playing with various configs</title>
				<link>https://sigtar.com/2009/07/18/zfs-playing-with-various-configs/</link>
				<pubDate>Sat, 18 Jul 2009 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2009/07/18/zfs-playing-with-various-configs/</guid>
				<description>&lt;p&gt;If you dont have the disks available to build up a zpool and have a play with zfs you can actually just use files created with the mkfile command&amp;hellip; The commands are exactly the same.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;mkfile 64m disk1&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;mkfile 64m disk2&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;mkfile 64m disk3&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;mkfile 10m disk4&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;mkfile 100m disk5&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;mkfile 100m disk6&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Now you can create a zpool using the above files&amp;hellip; (i&amp;rsquo;m using raidz for this setup)&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;zpool create test raidz /fullpath/disk1 /fullpath/disk2 /fullpath/disk3&lt;/strong&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>opensolaris - jumbo frames</title>
				<link>https://sigtar.com/2009/07/12/opensolaris-jumbo-frames/</link>
				<pubDate>Sun, 12 Jul 2009 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2009/07/12/opensolaris-jumbo-frames/</guid>
				<description>&lt;p&gt;If your keen on enabling jumbo frames in opensolaris this is the way&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://docs.sun.com/app/docs/doc/819-6990/gdyqk?l=en&amp;amp;a=view&#34;&gt;http://docs.sun.com/app/docs/doc/819-6990/gdyqk?l=en&amp;amp;a=view&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;# dladm show-phys&lt;/p&gt;&#xA;&lt;p&gt;LINK       MEDIA        STATE     SPEED     DUPLEX     DEVICE&lt;/p&gt;&#xA;&lt;p&gt;net0       ether        up        100Mb     full       bge0&lt;/p&gt;&#xA;&lt;p&gt;itops1     ether        up        100Mb     full       qfe3&lt;/p&gt;&#xA;&lt;p&gt;web1       ether        up        100Mb     full       bge1&lt;/p&gt;&#xA;&lt;p&gt;# dladm show-linkprop -p mtu web1&lt;/p&gt;&#xA;&lt;p&gt;LINK     PROPERTY     VALUE     DEFAULT     POSSIBLE&lt;/p&gt;&#xA;&lt;p&gt;web1     mtu          1500      1500        &amp;ndash;&lt;/p&gt;&#xA;&lt;p&gt;# ifconfig web1 unplumb&lt;/p&gt;&#xA;&lt;p&gt;# dladm set-linkprop -p mtu=9000 web1&lt;/p&gt;&#xA;&lt;p&gt;# ifconfig web1 plumb 10.10.1.2/24 up&lt;/p&gt;</description>
			</item>
			<item>
				<title>VirtualBox - Dup on ping</title>
				<link>https://sigtar.com/2009/06/22/virtualbox-dup-on-ping/</link>
				<pubDate>Mon, 22 Jun 2009 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2009/06/22/virtualbox-dup-on-ping/</guid>
				<description>&lt;p&gt;I&amp;rsquo;ve had this with certain kernels (2009.06) on opensolaris. Seems there is some incompatibility between some kernels and the opensolaris virtualbox network emulation. This only seems to effect linux virtual guests.&lt;/p&gt;&#xA;&lt;p&gt;When you try to ping an address you get something like this&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;[root@VA-DHCPWEB ~]# ping 192.168.9.15 PING 192.168.9.15 (192.168.9.15) 56(84) bytes of data. 64 bytes from 192.168.9.15: icmp_seq=1 ttl=128 time=1.85 ms 64 bytes from 192.168.9.15: icmp_seq=1 ttl=127 time=1.88 ms (DUP!)&lt;/em&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>Flashing si3114 to sata only bios</title>
				<link>https://sigtar.com/2009/05/20/flashing-si3114-to-sata-only-bios/</link>
				<pubDate>Wed, 20 May 2009 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2009/05/20/flashing-si3114-to-sata-only-bios/</guid>
				<description>&lt;p&gt;This is the perfect controller for adding additional sata drives into opensolaris (well in terms of price, the bandwidth of the PCI slot is the only negative part). The si3114 comes with the default bios that supports various raid configs, but this requires additional drivers to be loaded.&lt;/p&gt;&#xA;&lt;p&gt;Essentially the &amp;ldquo;raid&amp;rdquo; on the card is called fakeraid as it does not actually process any data itself, but hooks into the cpu via a driver and lets your cpu do all the work.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Opensolaris 2008.11 and xvm</title>
				<link>https://sigtar.com/2009/05/18/opensolaris-200811-and-xvm/</link>
				<pubDate>Mon, 18 May 2009 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2009/05/18/opensolaris-200811-and-xvm/</guid>
				<description>&lt;p&gt;I&amp;rsquo;ve been dabbling with virtual box up until this point. But have decided to take it to the next step by using xvm to run my virtual machines. I have taken a guide from BDerzhavets at this site : &lt;a href=&#34;http://bderzhavets.blogspot.com/2008/12/xvm-on-opensolaris-2008.html&#34;&gt;http://bderzhavets.blogspot.com/2008/12/xvm-on-opensolaris-2008.html&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;First step is to open package manager and find the &amp;ldquo;vitalization&amp;rdquo; grouping. Install everything in this group. You&amp;rsquo;ll probably find some packages are already installed.&lt;/p&gt;&#xA;&lt;p&gt;Next you&amp;rsquo;ll need to add the xvm kernel to the grub startup menu (menu.1st). This bit is a bit of blind faith from my perspective - its a shame that the xvm kernel package doesn&amp;rsquo;t add itself to grub? Anyhow&amp;hellip; You need to add the following as another boot option in the &lt;strong&gt;/rpool/boot/grub/menu.lst&lt;/strong&gt; file;&lt;/p&gt;</description>
			</item>
			<item>
				<title>Opensolaris : SMF and Squid</title>
				<link>https://sigtar.com/2009/05/16/opensolaris-smf-and-squid/</link>
				<pubDate>Sat, 16 May 2009 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2009/05/16/opensolaris-smf-and-squid/</guid>
				<description>&lt;p&gt;Decided to create a SMF manifest for squid so that it autostarts on boot.&lt;/p&gt;&#xA;&lt;p&gt;Command to start squid : &lt;strong&gt;/usr/squid/sbin/squid&lt;/strong&gt; &lt;/p&gt;&#xA;&lt;p&gt;Command to stop squid : &lt;strong&gt;/usr/squid/sbin/squid -k shutdown&lt;/strong&gt; &lt;/p&gt;&#xA;&lt;p&gt;This site has a good starter on SMF creation : &lt;a href=&#34;http://blogs.sun.com/observatory/entry/mouting_windows_shares_at_startup&#34;&gt;http://blogs.sun.com/observatory/entry/mouting_windows_shares_at_startup&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve taken a copy of the &lt;strong&gt;/var/svc/manifest/network/smb/server.xml&lt;/strong&gt; file for my squid manifest and placed it at &lt;strong&gt;/var/svc/manifest/network/squid/squid.xml&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Import the XML using this command; &lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;svccfg import /var/svc/manifest/network/squid/squid.xml&lt;/strong&gt; &lt;/p&gt;&#xA;&lt;p&gt;Update: i&amp;rsquo;ve stopped this work as i missed the fact that squid already comes with a SMF manifest! :)  No idea how i missed that one. You can enable via ; &lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;svcadm enable svc:/network/http:squid&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;This is the manifest for the above service; &lt;/p&gt;</description>
			</item>
			<item>
				<title>Opensolaris - configuring squid as a transparent proxy</title>
				<link>https://sigtar.com/2009/04/22/opensolaris-configuring-squid-as-transparent-proxy/</link>
				<pubDate>Wed, 22 Apr 2009 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2009/04/22/opensolaris-configuring-squid-as-transparent-proxy/</guid>
				<description>&lt;p&gt;I used to have a virtual machine that acted as a transparent proxy, but as of late thought i&amp;rsquo;d move squid onto my host box (opensolaris). This way hopefully increasing the amount of free ram available to the host while also taking advantage of ZFS etc&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;So this is a very brief guide on how to configure your opensolaris 2008.11 box as a transparent proxy. Essentially meaning if you set the solaris box as the default gateway all web traffic will be cached as it goes through it before it goes onto your dls router or outside connection.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Opensolaris - Managing Boot Environments with beadm</title>
				<link>https://sigtar.com/2009/03/31/opensolaris-managing-boot-environments-with-beadm/</link>
				<pubDate>Tue, 31 Mar 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/03/31/opensolaris-managing-boot-environments-with-beadm/</guid>
				<description>&lt;p&gt;To get a list of all of your boot environments within Opensolaris use &lt;strong&gt;beadm&lt;/strong&gt; like so…. &lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;beadm list&lt;/strong&gt; &lt;/p&gt;&#xA;&lt;p&gt;Assuming you know the name of the boot environment that is causing issues you can use the following command (using its name) to remove the ones you think are suss. Note: you need to boot up in the environment that you wish to keep first. &lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;beadm destroy &lt;em&gt;opensolaris-2&lt;/em&gt;&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;If you destroy an environment that is active on boot it will be changed to another be that is available. You can use the following command to set it to a specific boot environment; &lt;/p&gt;</description>
			</item>
			<item>
				<title>Opensolaris - where has my memory gone?</title>
				<link>https://sigtar.com/2009/03/28/opensolaris-where-has-my-memory-gone/</link>
				<pubDate>Sat, 28 Mar 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/03/28/opensolaris-where-has-my-memory-gone/</guid>
				<description>&lt;p&gt;Use this command in 2008.11 to get details on where your memory is currently being used&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;echo ::memstat | pfexec mdb -k&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;Page Summary                Pages                MB  %Tot &amp;mdash;&amp;mdash;&amp;mdash;&amp;mdash;     &amp;mdash;&amp;mdash;&amp;mdash;&amp;mdash;&amp;mdash;-  &amp;mdash;&amp;mdash;&amp;mdash;&amp;mdash;&amp;mdash;-  &amp;mdash;- Kernel                     263992              1031   34% ZFS File Data               91917               359   12% Anon                       376867              1472   48% Exec and libs               11484                44    1% Page cache                   3387                13    0% Free (cachelist)             9766                38    1% Free (freelist)             24807                96    3%&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;Total                      782220              3055 Physical                   782219              3055&lt;/em&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>Opensolaris - Updating solaris with the development repository</title>
				<link>https://sigtar.com/2009/03/27/opensolaris-updating-solaris-with-the-development-repository/</link>
				<pubDate>Fri, 27 Mar 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/03/27/opensolaris-updating-solaris-with-the-development-repository/</guid>
				<description>&lt;p&gt;Want to keep your opensolaris on the &amp;ldquo;edge&amp;rdquo; of developments? Most of the experience i have had is that the &amp;ldquo;dev&amp;rdquo; repository contains mainly stable releases that are being held until the next official release (every 6 months).&lt;/p&gt;&#xA;&lt;p&gt;This is how you do it&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;Launch Package Manager - and choose &amp;ldquo;settings&amp;rdquo; then &amp;ldquo;manage repositories&amp;rdquo;&lt;/p&gt;&#xA;&lt;p&gt;Add the dev repository URL and give it a name.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;NOTE: The name cannot contain any spaces!&lt;/strong&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>zfs - java management gui</title>
				<link>https://sigtar.com/2009/03/18/zfs-java-management-gui/</link>
				<pubDate>Wed, 18 Mar 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/03/18/zfs-java-management-gui/</guid>
				<description>&lt;p&gt;It hasn&amp;rsquo;t made it into opensolaris yet. But from what i&amp;rsquo;ve heard it should be making an appearance over from the solaris 10 OS soon. Here is a screenshot of what it looks like&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://sigtar.com/wp-content/uploads/2009/03/zfsscreenshot.jpg&#34; alt=&#34;zfsscreenshot&#34; title=&#34;zfsscreenshot&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Should make managing zfs a bit easier - though its already quite easy.  Perhaps if you have quite alot of zpools / zfs file systems it will look prettier.   ;)&lt;/p&gt;</description>
			</item>
			<item>
				<title>Troubleshooting - Time Slider (zfs snapshots)</title>
				<link>https://sigtar.com/2009/03/17/troubleshooting-time-slider-zfs-snapshots/</link>
				<pubDate>Tue, 17 Mar 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/03/17/troubleshooting-time-slider-zfs-snapshots/</guid>
				<description>&lt;p&gt;&lt;strong&gt;1. snapshot complains about no access to cron&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;This problem i came across was after i was playing with crontab. It looks like the zfs snapshot service uses an account called &amp;ldquo;zfssnap&amp;rdquo; and if it doesnt have access to cron then it will have issues creating / checking snapshots. Check the file &lt;strong&gt;/etc/cron.d/cron.allow&lt;/strong&gt; and ensure that &amp;ldquo;zfssnap&amp;rdquo; is in there. The issues i had looked like this in the log&amp;hellip;   (check the logs via the log file viewer)&lt;/p&gt;</description>
			</item>
			<item>
				<title>zfs - checking your zpool throughput</title>
				<link>https://sigtar.com/2009/02/18/zfs-checking-your-zpool-throughput/</link>
				<pubDate>Wed, 18 Feb 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/02/18/zfs-checking-your-zpool-throughput/</guid>
				<description>&lt;p&gt;This is quite a good diagnostic for checking your disk throughput. Try copying data to and from your zpool while your running this command on the host&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;zpool iostat -v unprotected 2&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;capacity     operations    bandwidth&#xA;pool         used  avail   read  write   read  write&#xA;----------  -----  -----  -----  -----  -----  -----&#xA;unprotected  1.39T   668G     18      7  1.35M   161K&#xA;c7d0       696G   403M      1      2  55.1K  21.3K&#xA;c9d0       584G   112G      8      2   631K  69.3K&#xA;c7d1       141G   555G      8      2   697K  70.0K&#xA;----------  -----  -----  -----  -----  -----  -----&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;The above command will keep displaying the above output every 2 seconds (average during that time). I&amp;rsquo;ve used it a few times to ensure that all disks are being used (in write operations) where needed. Of course read op&amp;rsquo;s may not be typically across all disks as it will depend where the data is&amp;hellip;&lt;/p&gt;</description>
			</item>
			<item>
				<title>OpenSolaris cifs/smb server - configuring ACL’s on shares - Part 2</title>
				<link>https://sigtar.com/2009/02/15/opensolaris-cifssmb-server-configuring-acls-on-shares-part-2/</link>
				<pubDate>Sun, 15 Feb 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/02/15/opensolaris-cifssmb-server-configuring-acls-on-shares-part-2/</guid>
				<description>&lt;p&gt;I have done most of the explaining in another post on how the permissions work with a zfs cifs share - &lt;a href=&#34;https://sigtar.com/2009/02/14/opensolaris-cifssmb-server-configuring-acls-on-shares/&#34;&gt;link here&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;In this post I&amp;rsquo;m going to show an example of how to add multiple groups / users to a specific folder. Which then recursively adds its ACL&amp;rsquo;&amp;rsquo;s to any child objects. Its essentially like the other commands i used, but with an extra line per user or group you want to configure; &lt;/p&gt;</description>
			</item>
			<item>
				<title>OpenSolaris cifs/smb server - configuring ACL&#39;s on shares</title>
				<link>https://sigtar.com/2009/02/14/opensolaris-cifssmb-server-configuring-acls-on-shares/</link>
				<pubDate>Sat, 14 Feb 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/02/14/opensolaris-cifssmb-server-configuring-acls-on-shares/</guid>
				<description>&lt;p&gt;O.k. from this  point I&amp;rsquo;m assuming you have created your zfs shares via the &lt;strong&gt;zfs&lt;/strong&gt; command and renamed appropriately like so&amp;hellip;..   (&lt;a href=&#34;https://sigtar.com/2009/02/13/opensolaris-migrating-from-samba-to-cifs/&#34;&gt;if you havent setup cifs yet then check read this&lt;/a&gt;)&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;zfs set sharesmb=on protected/backup&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;zfs set sharesmb=name=backup protected/backup&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Now to check your current shares type&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;sharemgr show&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;zfs&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;zfs/protected/backup backup=/protected/backup&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;zfs/protected/photos photos=/protected/photos&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;Now its time to look at NFSv4 ACL&amp;rsquo;s. This page has a great explanation of ACL&amp;rsquo;s and how to set things up. &lt;a href=&#34;http://cuddletech.com/blog/pivot/entry.php?id=939&#34;&gt;http://cuddletech.com/blog/pivot/entry.php?id=939&lt;/a&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>OpenSolaris - Migrating from samba to cifs</title>
				<link>https://sigtar.com/2009/02/13/opensolaris-migrating-from-samba-to-cifs/</link>
				<pubDate>Fri, 13 Feb 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/02/13/opensolaris-migrating-from-samba-to-cifs/</guid>
				<description>&lt;p&gt;OpenSolaris 2008.11 has a cifs/smb server built into the kernel. From what i have been reading (and discovering) this is a much more efficient and faster way to get your files out into the network.&lt;/p&gt;&#xA;&lt;p&gt;Previously i have run a dedicated samba service to share my files as I&amp;rsquo;ve come from various linux distros which require it. Seems i should be doing things differently on OpenSolaris.&lt;/p&gt;&#xA;&lt;p&gt;The dedicated samba service is called;&lt;/p&gt;</description>
			</item>
			<item>
				<title>OpenSolaris - RTL8111/8168B issues</title>
				<link>https://sigtar.com/2009/02/12/opensolaris-rtl81118168b-issues/</link>
				<pubDate>Thu, 12 Feb 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/02/12/opensolaris-rtl81118168b-issues/</guid>
				<description>&lt;p&gt;I&amp;rsquo;ve got an integrated RTL8111 nic which seemed to work fine under opensolaris 2008.11. But if the nic was put under load for a various length of time it seemed to just drop off the network.&lt;/p&gt;&#xA;&lt;p&gt;At first i thought it was my SMB service dying, but after a quick ping i relised i had lost the entire TCP/IP stack on that particular card. Hmm&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;It does come back online if you are patient and wait for about 5mins or so.&lt;/p&gt;</description>
			</item>
			<item>
				<title>OpenSolaris - Manual Network DNS issue</title>
				<link>https://sigtar.com/2009/02/11/opensolaris-manual-network-config-issue/</link>
				<pubDate>Wed, 11 Feb 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/02/11/opensolaris-manual-network-config-issue/</guid>
				<description>&lt;p&gt;If you have tried to setup a manual IP on your opensolaris box you may find that DNS is not working as you would expect in some cases. &lt;strong&gt;nslookup&lt;/strong&gt; resolves the name to an ip, but &lt;strong&gt;ping&lt;/strong&gt;ing doesnt make it to the box&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;How to fix;&lt;/p&gt;&#xA;&lt;p&gt;Edit your &lt;strong&gt;/etc/nsswitch.conf&lt;/strong&gt; file and add the word &amp;ldquo;&lt;strong&gt;dns&lt;/strong&gt;&amp;rdquo; to the &lt;strong&gt;hosts&lt;/strong&gt; and &lt;strong&gt;ipnodes&lt;/strong&gt; lines If you make a backup of &lt;strong&gt;/etc/nsswitch.conf&lt;/strong&gt; you can also just copy &lt;strong&gt;/etc/nsswitch.dns&lt;/strong&gt; over it&amp;hellip;&lt;/p&gt;</description>
			</item>
			<item>
				<title>ZFS - Creating snapshots</title>
				<link>https://sigtar.com/2009/02/09/zfs-creating-snapshots/</link>
				<pubDate>Mon, 09 Feb 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/02/09/zfs-creating-snapshots/</guid>
				<description>&lt;p&gt;There is some funky ways of modifying the default &amp;ldquo;time slider&amp;rdquo; services to do the work for you, but i like a bit more hands on. Generally so i know what is happening in the background, but the time slider can be sometimes overkill creating snapshots every 15 mins if not configured properly.&lt;/p&gt;&#xA;&lt;p&gt;On a side note i&amp;rsquo;ve yet to get my head around the SMF stuff properly&amp;hellip; Anyhow onto creating snapshots.&lt;/p&gt;</description>
			</item>
			<item>
				<title>ZFS - Removing all snapshots</title>
				<link>https://sigtar.com/2009/02/08/zfs-removing-all-snapshots/</link>
				<pubDate>Sun, 08 Feb 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/02/08/zfs-removing-all-snapshots/</guid>
				<description>&lt;p&gt;To list all of your current snapshots;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;zfs list -t snapshot&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;This is a handy script to remove all snapshots&amp;hellip;.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;for snapshot in `zfs list -H -t snapshot | cut -f 1` do zfs destroy $snapshot done&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;As always : at your own risk. ;)&lt;/p&gt;</description>
			</item>
			<item>
				<title>Linux - crontab</title>
				<link>https://sigtar.com/2009/02/03/linux-crontab/</link>
				<pubDate>Tue, 03 Feb 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/02/03/linux-crontab/</guid>
				<description>&lt;p&gt;Time to schedule some tasks!&lt;/p&gt;&#xA;&lt;p&gt;First you need to make sure your in the &lt;strong&gt;/etc/cron.d/cron.allow&lt;/strong&gt; file. If you are not &lt;strong&gt;SU&lt;/strong&gt; to root and add yourself into it.&lt;/p&gt;&#xA;&lt;p&gt;Now to create your new crontab file;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;crontab -e&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;You are in &lt;strong&gt;vi&lt;/strong&gt; in your newly created crontab file (note if you do not have access to do this it will say so)&lt;/p&gt;&#xA;&lt;p&gt;Now, i&amp;rsquo;m no expert at using &lt;strong&gt;vi&lt;/strong&gt;, but if you press &lt;strong&gt;i&lt;/strong&gt; you will go into insert mode. Do this, then type the cron job details. A typical cron job will look like this&lt;/p&gt;</description>
			</item>
			<item>
				<title>ZFS - Error 16 : Inconsistent filesystem structure</title>
				<link>https://sigtar.com/2009/02/02/zfs-error-16-inconsistent-filesystem-structure/</link>
				<pubDate>Mon, 02 Feb 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/02/02/zfs-error-16-inconsistent-filesystem-structure/</guid>
				<description>&lt;p&gt;Oh no. I&amp;rsquo;ve managed to get this error before. And it was right after i applied compression to the &lt;strong&gt;rpool&lt;/strong&gt; zfs filesystem. Upon the next reboot i was greeted with this error message;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Error 16 : Inconsistent filesystem structure&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;For me it was a show stopper and i had to go into recovery. So i&amp;rsquo;ve learnt my lesson - Not to touch the rpool zpool.&lt;/p&gt;&#xA;&lt;p&gt;I was lucky enough to have put my data within a zfs filesystem (rpool/virtual) i created within the default rpool zpool.  I use this spot for my VirtualBox virtual machines.&lt;/p&gt;</description>
			</item>
			<item>
				<title>ZFS basics</title>
				<link>https://sigtar.com/2009/01/30/zfs-basics/</link>
				<pubDate>Fri, 30 Jan 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/01/30/zfs-basics/</guid>
				<description>&lt;p&gt;I&amp;rsquo;ve had a play with WHS but eventually got annoyed with its lack of performance. Yes i know its not built for performance and typically is used just as a backup / simple store with duplication as redundancy, just i couldn&amp;rsquo;t stand the speed of the thing. If you were ever unlucky enough (even post power pack 1) to do a copy during the &amp;ldquo;data moving&amp;rdquo; the performance was even worse. On a positive note nothing beats it if you have a heap of non-similar sized disks that you want to put together (with redundancy) as a single shared storage pool.&lt;/p&gt;</description>
			</item>
			<item>
				<title>ZFS compression types</title>
				<link>https://sigtar.com/2009/01/30/zfs-compression-types/</link>
				<pubDate>Fri, 30 Jan 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/01/30/zfs-compression-types/</guid>
				<description>&lt;p&gt;ZFS compression as of OpenSolaris 2008.11 has a few types to choose from.&lt;/p&gt;&#xA;&lt;p&gt;lzjb (default) | gzip | gzip-[1-9]&lt;/p&gt;&#xA;&lt;p&gt;They are used via the &lt;strong&gt;zfs set compression=gzip&lt;/strong&gt; &lt;em&gt;&lt;strong&gt;poolname&lt;/strong&gt; command.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;The following test was quickly done out of personal interest - and is in no way scientific!&lt;/p&gt;&#xA;&lt;p&gt;I have a AMD cpu with 3 cores (2.4Ghz). The data i copied to each of the shares consisted of video / documents / pictures and music. The first test i have done is based on compression only (i have not measured throughput)&lt;/p&gt;</description>
			</item>
			<item>
				<title>OpenSolaris - Autologon</title>
				<link>https://sigtar.com/2009/01/29/open-solaris-autologin/</link>
				<pubDate>Thu, 29 Jan 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/01/29/open-solaris-autologin/</guid>
				<description>&lt;p&gt;There are two ways to setup the auto login for OpenSolaris (2008.11);&lt;/p&gt;&#xA;&lt;p&gt;One - You can fire up the GUI using &lt;strong&gt;gdmsetup.&lt;/strong&gt; Update : this didnt actually work when i tried it recentely - it might not be in this release of opensolaris.&lt;/p&gt;&#xA;&lt;p&gt;Two - go to &lt;strong&gt;/etc/x****11/gdm/custom.conf&lt;/strong&gt; (in newer releases its just /&lt;strong&gt;etc/gdm/custom.conf&lt;/strong&gt;) and manually modify the required fields in the [daemon] section and add the following;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;[daemon] AutomaticLoginEnable=true AutomaticLogin=username&lt;/strong&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>OpenSolaris - SMF and VirtualBox</title>
				<link>https://sigtar.com/2009/01/29/smf-and-virtualbox/</link>
				<pubDate>Thu, 29 Jan 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/01/29/smf-and-virtualbox/</guid>
				<description>&lt;p&gt;So&amp;hellip; i&amp;rsquo;m looking for a way to fire up some VirtualBox machines after a reboot on OpenSolaris. SMF is the key. Just need to create some XML docs that fire up a couple of headless vm&amp;rsquo;s.&lt;/p&gt;&#xA;&lt;p&gt;Shouldn&amp;rsquo;t be too hard. Lets see what i can come up with.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://mediacast.sun.com/users/netherton/media/SMF-migrate.pdf&#34;&gt;Here is a good pdf about migrating Legacy RC services into SMF, which has given me a few pointers&lt;/a&gt;&amp;hellip;. &lt;/p&gt;&#xA;&lt;p&gt;how to shutdown a vm;&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
