<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Storage on sigtar.com</title>
		<link>https://sigtar.com/categories/storage/</link>
		<description>Recent content in Storage on sigtar.com</description>
		<generator>Hugo</generator>
		<language>en-nz</language>
		
		
		
		
			<lastBuildDate>Thu, 30 Oct 2014 00:00:00 +1300</lastBuildDate>
		
			<atom:link href="https://sigtar.com/categories/storage/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>unraid smart check - dead WD green drive</title>
				<link>https://sigtar.com/2014/10/30/unraid-smart-check/</link>
				<pubDate>Thu, 30 Oct 2014 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2014/10/30/unraid-smart-check/</guid>
				<description>&lt;p&gt;errors on unraid GUI - sometimes its a loose cable, sometimes its an issue with the drive.&lt;/p&gt;&#xA;&lt;p&gt;Run this command to check smart status&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;smartctl -a -d ata /dev/sda&lt;/strong&gt; or if you are using a newer SATA controller &lt;strong&gt;smartctl -a -A /dev/sda&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://lime-technology.com/wiki/index.php/Troubleshooting&#34;&gt;http://lime-technology.com/wiki/index.php/Troubleshooting&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;unfortunately in my case, looks like drive is pretty much dead&amp;hellip; not too bad for a drive almost 5 years old.&lt;/p&gt;&#xA;&lt;p&gt;its pretty typical of a WD green drive in its default config to die in this type of environment, no plans to replace it with a similar type drive. You can see below the incredibly high LCC count which indicates the drive header has parked this many times over its life. This is probably part of the problem - there is a tool you can run (check this vid, link for  WDIDDLE3 also in comments - &lt;a href=&#34;http://www.youtube.com/watch?v=J2eYyRI_F98&#34;&gt;http://www.youtube.com/watch?v=J2eYyRI_F98&lt;/a&gt;) which disables the intellipark feature of the green drive. I never disabled the park timeout before this drive died (which defaults to 8 seconds!) &amp;ndash; note: i have disabled it completely on my other green drives.&lt;/p&gt;</description>
			</item>
			<item>
				<title>windows 2012 - dedup</title>
				<link>https://sigtar.com/2013/08/07/windows-2012-dedup/</link>
				<pubDate>Wed, 07 Aug 2013 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2013/08/07/windows-2012-dedup/</guid>
				<description>&lt;p&gt;If you have some archive data that you would like to copy onto a  win 2012 server, but dont know how to estimate the end volume size (if VM etc). Start small - about 1/2 of the total capacity of the drive. Robocopy the data onto the drive until nearly full, manually run dedupe, wait until complete, continue robocopy, repeat and rinse. There will be occasions where you will run out of disk space at that point its time to extend your disk.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Equallogic - 6.0 Feature List</title>
				<link>https://sigtar.com/2013/07/28/equallogic-6-0-feature-list/</link>
				<pubDate>Sun, 28 Jul 2013 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2013/07/28/equallogic-6-0-feature-list/</guid>
				<description>&lt;p&gt;&lt;a href=&#34;http://www.dell.com/learn/us/en/04/campaigns/equallogic-software&#34;&gt;http://www.dell.com/learn/us/en/04/campaigns/equallogic-software&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Features introduced in release 6.0:&lt;/p&gt;&#xA;&lt;p&gt;• Synchronous Replication • Snapshot Space Borrowing • Volume Unmap • Volume Undelete • Support for SED drives and IPsec&lt;/p&gt;&#xA;&lt;p&gt;Features you have come to rely on:&lt;/p&gt;&#xA;&lt;p&gt;• Data Center Bridging • Automatic load balancing • VMware® Thin Provisioning awareness • Auditing of administrative actions • Microsoft® Active Directory integration • Peer storage architecture • Rapid provisioning • Storage pools • Roles-based administration • Thin clones • SAN Data Copy Offload • SAN Zero Offload and Scalable Lock Management for VMware • Intelligent tiering of data across models that combine solid-state drive (SSD) and hard drives • Integration with the VMware® vStorage APIs • Nondisruptive array upgrades • Nondisruptive array removal • Online data and volume movement • Automatic RAID placement • Thin provisioning • Instant volume restore • Multivolume, writable snapshots • Snapshot and point-in-time replication scheduler • Volume cloning • Volume consistency sets • Auto-start disk monitoring system • Email home • Enclosure monitoring system • Performance monitoring&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>Why is UNRAID cool for home?</title>
				<link>https://sigtar.com/2013/05/18/why-is-unraid-cool-for-home/</link>
				<pubDate>Sat, 18 May 2013 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2013/05/18/why-is-unraid-cool-for-home/</guid>
				<description>&lt;p&gt;I&amp;rsquo;ve played with many storage technologies at home, ZFS being one of my favs when it comes to performance. But i&amp;rsquo;ve been looking for something that suits a typical home environment where power usage and capacity is usually more important than performance. Thats where UNRAID has come in&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;UNRAID give me these advantages;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Different sized disks in a single pool (only requires largest disk as parity)&lt;/li&gt;&#xA;&lt;li&gt;Files are distributed over all the disks - so even if you lost more than a single drive you still still have some of your data. Note : with parity drive you can handle a single drive failing without loosing anything, sorta like RAID4 - non distributed parity.&lt;/li&gt;&#xA;&lt;li&gt;Power usage, since the files are stored on specific disks not all the disks need to power on to give you your file.&lt;/li&gt;&#xA;&lt;li&gt;Runs on a USB stick - no large operating system required.&lt;/li&gt;&#xA;&lt;li&gt;Crashplan module can be installed to provide backup options.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://lime-technology.com/&#34;&gt;http://lime-technology.com/&lt;/a&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>short stroking - v2</title>
				<link>https://sigtar.com/2011/11/28/short-stroking-v2/</link>
				<pubDate>Mon, 28 Nov 2011 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2011/11/28/short-stroking-v2/</guid>
				<description>&lt;p&gt;I&amp;rsquo;ve run through this exercise again - my old findings &lt;a href=&#34;https://sigtar.com/2009/12/21/hdd-short-stroking-is-it-worth-it/&#34;&gt;here&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;4 x 500 WD Black drives &amp;ndash; in one big RAID 0 (128K blocks)&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://sigtar.com/wp-content/uploads/2011/11/HDTune_Benchmark_Intel___Raid_0_Volume.png&#34;&gt;&lt;img src=&#34;https://sigtar.com/wp-content/uploads/2011/11/HDTune_Benchmark_Intel___Raid_0_Volume.png&#34; alt=&#34;&#34; title=&#34;HDTune_Benchmark_Intel___Raid_0_Volume&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;and again only using 500GB of capacity (roughly 1/4 of each of the drives)&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://sigtar.com/wp-content/uploads/2011/11/HDTune_Benchmark_Intel___Raid_.25_0_Volume.png&#34;&gt;&lt;img src=&#34;https://sigtar.com/wp-content/uploads/2011/11/HDTune_Benchmark_Intel___Raid_.25_0_Volume.png&#34; alt=&#34;&#34; title=&#34;HDTune_Benchmark_Intel___Raid_.25_0_Volume&#34;&gt;&lt;/a&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>P4000 / Lefthand - v9.5 feature list</title>
				<link>https://sigtar.com/2011/10/10/p4000-lefthand-v9-5-feature-list/</link>
				<pubDate>Mon, 10 Oct 2011 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2011/10/10/p4000-lefthand-v9-5-feature-list/</guid>
				<description>&lt;p&gt;The 9.5 release is a comprehensive release that includes enhancements in the following areas:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Application managed snapshots for VMware ESX Server and Microsoft Hyper-V Server&lt;/li&gt;&#xA;&lt;li&gt;SAN Status Home Page — the SAN Status home page is the new home page for the CMC and presents key information for all management groups in the storage environment in a single view.&lt;/li&gt;&#xA;&lt;li&gt;Zero to VSA automated installation and deployment — Single installer can install VSA, FOM and CMC. Go from “zero” to a fully functional virtual SAN in just a few easy steps. Scriptable install tool allows ROBO customers to script install once and deploy VSA quickly at multiple remote locations.&lt;/li&gt;&#xA;&lt;li&gt;Peer Motion data mobility with cluster swap — Cluster swap allows users to replace or upgrade P4000 clusters. Edit cluster menu guides decisions about adding, removing, or exchanging storage systems. Easily migrate data online between tiers.&lt;/li&gt;&#xA;&lt;li&gt;Remote Copy performance improvements — Improvements to remote copy times, the time required to scan volumes, ability to support more frequent snapshots, reduction of RPOs for DR solutions.&lt;/li&gt;&#xA;&lt;li&gt;Storage Replication Adapter for Vsphere Site Recovery Manager 5.x — Supports automated failback and is included on the HP P4000 Application Integration Solution Pack&lt;/li&gt;&#xA;&lt;li&gt;Best Practice configuration wizards — Configuration wizards guide towards highest availability configurations: add Failover Manager for 2–node configuration, configure disk RAID 6 for single-node configurations, recommends volume replication when expanding clusters to more than one storage system&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
			</item>
			<item>
				<title>allow root ssh login solaris 11 express</title>
				<link>https://sigtar.com/2011/07/27/allow-root-ssh-login-solaris-11-express/</link>
				<pubDate>Wed, 27 Jul 2011 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2011/07/27/allow-root-ssh-login-solaris-11-express/</guid>
				<description>&lt;p&gt; &lt;/p&gt;&#xA;&lt;p&gt;Change SSHD to allow root login;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;vi /etc/ssh/sshd_config PermitRootLogin = yes&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Allow remote logon for root user, comment out the following line;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;vi /etc/default/login&lt;/strong&gt; **&lt;/p&gt;&#xA;&lt;p&gt;#CONSOLE =/dev/login&lt;/p&gt;&#xA;&lt;p&gt;**&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;rolemod -K type=normal root&lt;/strong&gt;&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>enable TRIM in windows 7</title>
				<link>https://sigtar.com/2011/06/19/enable-trim-in-windows-7/</link>
				<pubDate>Sun, 19 Jun 2011 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2011/06/19/enable-trim-in-windows-7/</guid>
				<description>&lt;p&gt;This command will confirm if TRIM has been auto-enabled by windows 7&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;fsutil behavior query disabledeletenotify&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;DisableDeleteNotify = 1 (Windows TRIM commands are disabled) DisableDeleteNotify = 0 (Windows TRIM commands are enabled)&lt;/p&gt;&#xA;&lt;p&gt;If you would like to force it on;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;fsutil behavior set disabledeletenotify 0&lt;/strong&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>P4000 / Lefthand and Windows DSM (MPIO)</title>
				<link>https://sigtar.com/2011/05/04/p4000-lefthand-and-windows-dsm-mpio/</link>
				<pubDate>Wed, 04 May 2011 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2011/05/04/p4000-lefthand-and-windows-dsm-mpio/</guid>
				<description>&lt;p&gt;Steps to setup MPIO round robin and DSM with P4000 / Lefthand nodes&lt;/p&gt;&#xA;&lt;p&gt;This example is windows 2008 with 2 x 1gbit nics&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;Install HP DSM driver onto windows 2008  (this should also install MPIO feature on windows 2008)&lt;/li&gt;&#xA;&lt;li&gt;Setup 2 x IP&amp;rsquo;s on windows host - storage subnet (used with MPIO)&#xA;&lt;ol&gt;&#xA;&lt;li&gt;Confirm you can ping target from both (enable one at a time - ensure there is no routing on your other nics)&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Provision storage and allow server read / write access to windows server (via initiator name)&lt;/li&gt;&#xA;&lt;li&gt;Open iSCSI on windows 2008&lt;/li&gt;&#xA;&lt;li&gt;Put in IP of target in discovery tab&lt;/li&gt;&#xA;&lt;li&gt;On first tab confirm that iSCSI drive is presented to host&lt;/li&gt;&#xA;&lt;li&gt;Click &amp;ldquo;connect&amp;rdquo; - check both auto-connect and use MPIO&#xA;&lt;ol&gt;&#xA;&lt;li&gt;click advanced - chose MS iSCSI initiator, choose first IP and target IP. Click o.k. / o.k&lt;/li&gt;&#xA;&lt;li&gt;click advanced - chose MS iSCSI initiator, choose second IP and target IP. Click o.k. / o.k&lt;/li&gt;&#xA;&lt;li&gt;Repeat above per additional Nic&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Confirm via &amp;ldquo;devices&amp;rdquo; that there is x (as many targets as nics) targets per disk&#xA;&lt;ol&gt;&#xA;&lt;li&gt;Within devices choose MPIO - change from vendor specific to &amp;ldquo;round robin&amp;rdquo;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;Note : read / write access to LUN is required when using &amp;ldquo;round robin&amp;rdquo; MPIO opposed to the default &amp;ldquo;vendor specific&amp;rdquo; which works with read only access. Else you will get an error - &amp;ldquo;not supported&amp;rdquo;&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Repeat above per &amp;ldquo;device&amp;rdquo;&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Confirm on Lefthand / P4000 CMC that the LUN has one connection per initiator Nic, and that each connection also has its DSM children (visible in CMC if working).&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;Confirm that the connection are as expected&amp;hellip;&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>vmware - finding orphaned files</title>
				<link>https://sigtar.com/2011/01/21/vmware-finding-orphaned-files/</link>
				<pubDate>Fri, 21 Jan 2011 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2011/01/21/vmware-finding-orphaned-files/</guid>
				<description>&lt;p&gt;Use following script for finding orphaned files in your vmware env&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;&lt;code&gt;# # Purpose : List all orphaned vmdk on all datastores in all VC&#39;s # Version: 1.1 # Author : HJA van Bokhoven # Modifications: LucD&lt;/code&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;code&gt;$arrayVC = @(“server”) $report = @()&lt;/code&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;code&gt;foreach ($strVC in $arrayVC) { Connect-VIServer $strVC $arrUsedDisks = Get-View -ViewType VirtualMachine | % {$_.Layout} | % {$_.Disk} | % {$_.DiskFile} $arrDS = Get-Datastore | Sort-Object -property Name foreach ($strDatastore in $arrDS) { Write-Host $strDatastore.Name $ds = Get-Datastore -Name $strDatastore.Name | % {Get-View $_.Id} $fileQueryFlags = New-Object VMware.Vim.FileQueryFlags $fileQueryFlags.FileSize = $true $fileQueryFlags.FileType = $true $fileQueryFlags.Modification = $true $searchSpec = New-Object VMware.Vim.HostDatastoreBrowserSearchSpec $searchSpec.details = $fileQueryFlags $searchSpec.matchPattern = &amp;quot;*.vmdk&amp;quot; $searchSpec.sortFoldersFirst = $true $dsBrowser = Get-View $ds.browser $rootPath = &amp;quot;[&amp;quot;+$ds.summary.Name+&amp;quot;]&amp;quot;&lt;/code&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>Vmware &amp; HP MSA</title>
				<link>https://sigtar.com/2011/01/21/vmware-hp-msa/</link>
				<pubDate>Fri, 21 Jan 2011 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2011/01/21/vmware-hp-msa/</guid>
				<description>&lt;p&gt;Here is a great guide on multipathing and iSCSI MSA&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://jpaul.me/?tag=vmware-multipathing&#34;&gt;http://jpaul.me/?tag=vmware-multipathing&lt;/a&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>Celerra - Unable to create, refresh, or delete checkpoint of a replicated destination file system</title>
				<link>https://sigtar.com/2010/11/09/celerra-unable-to-create-refresh-or-delete-checkpoint-of-a-replicated-destination-file-system/</link>
				<pubDate>Tue, 09 Nov 2010 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2010/11/09/celerra-unable-to-create-refresh-or-delete-checkpoint-of-a-replicated-destination-file-system/</guid>
				<description>&lt;p&gt;I&amp;rsquo;ve been stuck with this error recently on a Celerra manager device : DpRequest_Max_VS_SuspendedCheckpointsReached&lt;/p&gt;&#xA;&lt;p&gt;This can sometimes happen when a filesystem is held during a replication task. To check what filesystems are currently being replcated run the following command;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;nas_replicate -info -all&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Either wait until the replication has completed - check status. Or temporary stop the replication task (stop it from the source side if possible).&lt;/p&gt;</description>
			</item>
			<item>
				<title>EMC Celerra Optimizations for VMware on NFS</title>
				<link>https://sigtar.com/2010/10/12/emc-celerra-optimizations-for-vmware-on-nfs/</link>
				<pubDate>Tue, 12 Oct 2010 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2010/10/12/emc-celerra-optimizations-for-vmware-on-nfs/</guid>
				<description>&lt;p&gt;go here &lt;a href=&#34;http://blog.scottlowe.org/2010/01/31/emc-celerra-optimizations-for-vmware-on-nfs/&#34;&gt;http://blog.scottlowe.org/2010/01/31/emc-celerra-optimizations-for-vmware-on-nfs/&lt;/a&gt;&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;Turn on the uncached write mechanism for NFS file systems used as VMware datastores. This can have a significant performance improvement for VMDKs on NFS but isn’t the default setting. From the Control Station, you can use this command to turn on the uncached write mechanism: &lt;code&gt;server_mount &amp;lt;data mover name&amp;gt; -option &amp;lt;options&amp;gt;,**uncached** &amp;lt;file system name&amp;gt; &amp;lt;mount point&amp;gt;&lt;/code&gt; Be sure to review pages 99 through 101 of the VMware on Celerra best practices document for more information on the uncached write mechanism and any considerations for its use.&lt;/p&gt;&#xA;&lt;/blockquote&gt;</description>
			</item>
			<item>
				<title>vmware and load balancing NFS trunks</title>
				<link>https://sigtar.com/2010/09/22/vmware-and-load-balancing-nfs-trunks/</link>
				<pubDate>Wed, 22 Sep 2010 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2010/09/22/vmware-and-load-balancing-nfs-trunks/</guid>
				<description>&lt;p&gt;Straight from the post below, this is the best way (currently) to load balance your NFS datastores&amp;hellip;  No MPIO magic here unfortunately.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://communities.vmware.com/message/1466595#1466595&#34;&gt;http://communities.vmware.com/message/1466595#1466595&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Basically you can setup IP alias on the NFS side and then setup multiple connections (using a unique IP) per datastore  on each ESX host. This works well if you are using a team of nics running IP-hash load balancing&amp;hellip;&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;Static EtherChannel.&lt;/p&gt;&#xA;&lt;p&gt;My setup is as follows:&lt;/p&gt;&#xA;&lt;p&gt;ESXi 4.0 U1, Cisco 3750 Switches, and NetApp NFS on the storage side.&lt;/p&gt;&#xA;&lt;p&gt;I have a total of 8 nics. I divided the nics into 3 groups.&lt;/p&gt;&#xA;&lt;p&gt;2 nics on vSwitch0 for Mgmt &amp;amp; vMotion 3 nics on vSwitch1 for VM&amp;rsquo;s (Multiple port groups (3 VLANS)) 3 nics on vSwitch2 for IP Storage (Mostly NFS, a little iSCSI) (One vSwitch3 I also have a VM port group for iSCSI access from within the VM)&lt;/p&gt;&#xA;&lt;p&gt;Since I have 3 nics on my IPStorage port group I needed a way to be able to utilize all three nics and not have the server just use one for ingress and egress traffic. This was done by:&lt;/p&gt;&#xA;&lt;p&gt;Setting up a static EtherChannel on the cisco switch (Port Channel). Configuring the cisco switch to IP Hash Configure the vSwitch to &amp;ldquo;Route based on IP Hash&amp;rdquo; as well.&lt;/p&gt;&#xA;&lt;p&gt;The next part is to create multiple datastores on the NFS device. Each of my NFS datastores is about 500GB in size. Reason for this is that my larger luns are iSCSI and are access directly from the VM using the MS iSCSI initiator from the VM itself. My NetApp NAS has an address of, let say, 192.168.1.50. So all my data stores are accessible by utilizing the address of &amp;ldquo;\\192.168.1.50\NFS-Store#&amp;rdquo;. This will not be useful as the esx box and the cisco switch will always use the same nic/port to access the nas device. This is due to the algorithm (IP HASH) to decide what link it&amp;rsquo;ll go over. So to resolve the issue, I added IP aliases to the NFS box. NetApp allows to have multiple Ip addresses pointing to the same NFS export, I suspect EMC would do the same. So, I added 2 aliases 51 &amp;amp; 52. Now my NFS datastores are accessible by using Ip address 192.168.1.50,.51, &amp;amp; .52.&lt;/p&gt;&#xA;&lt;p&gt;So I went ahead and added the datastores to the ESX box using the multiple IP addresses:&lt;/p&gt;&#xA;&lt;p&gt;Datastore1 = \\192.168.1.50\NFS-Store1 Datastore2 = \\192.168.1.51\NFS-Store2 Datastore3 = \\192.168.1.52\NFS-Store3&lt;/p&gt;&#xA;&lt;p&gt;If you have more datastores it&amp;rsquo;ll just repeat: Datastore4 = \\192.168.1.50\NFS-Store4 and so on&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;Since having multiple datastores and address to each, the 3 nics on the ESX box dedicated to IP Storage get utilized. It does not aggregate the bandwidth but it does use all three to send and recieve packets. So the fastest speed you will get is 1Gbit, theoretically, each way for traffic but, it is better than trying to cram all the traffic over 1 nic.&lt;/p&gt;&#xA;&lt;p&gt;I also enabled Jumbo Frames on the vSwitch as well as the vmNic for IP-Stroage. (need the best performance!) I should mention that your NFS storage device should have EtherChannel setup on it as well. Otherwise, you&amp;rsquo;ll be on the same boat just on the other end of it.&lt;/p&gt;&#xA;&lt;p&gt;Hope it helps!&lt;/p&gt;&#xA;&lt;p&gt;Larry B.&lt;/p&gt;&#xA;&lt;p&gt;I should mention that you should not use different addresses to access the same NFS share (datastore). It is not supported and may cause you issues.&lt;/p&gt;&#xA;&lt;/blockquote&gt;</description>
			</item>
			<item>
				<title>vmware srm - replicating over a wan - optimizations</title>
				<link>https://sigtar.com/2010/08/17/vmware-srm-replicating-over-a-wan-optimizations/</link>
				<pubDate>Tue, 17 Aug 2010 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2010/08/17/vmware-srm-replicating-over-a-wan-optimizations/</guid>
				<description>&lt;p&gt;I&amp;rsquo;ve been working through a SRM setup and have been looking at ways to optimize the amount of traffic that is sent over the WAN. The first obvious move is to move your vmware swap files off the replicated LUNS.&lt;/p&gt;&#xA;&lt;p&gt;Another way is to reduce the sync window. i.e. how often is yoru replication technology trying to keep the source and destination in sync? &amp;ndash; Increasing this window can sometimes help you out. But that all depends on your delta&amp;rsquo;s.&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 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>iometer testing</title>
				<link>https://sigtar.com/2010/03/26/iometer-testing/</link>
				<pubDate>Fri, 26 Mar 2010 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2010/03/26/iometer-testing/</guid>
				<description>&lt;p&gt;The following is some notes i have around the parameters i usually use during testing. There is a good document at ixbt labs on the various tests and settings&amp;hellip;.&lt;/p&gt;&#xA;&lt;p&gt;For a 1GB test set the sectors to : 2048000&lt;/p&gt;&#xA;&lt;p&gt;Typical benchmarks; (which you will need to add)&lt;/p&gt;&#xA;&lt;p&gt;128K 100% Read - Sequential&lt;/p&gt;&#xA;&lt;p&gt;128K 100% Write - Sequential&lt;/p&gt;&#xA;&lt;p&gt;Remember to bump the workers up to 5 or so. You can set the mixes across all the workers if you select the PC object.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Jumbo Frames on your vSphere ESXi box</title>
				<link>https://sigtar.com/2010/03/02/jumbo-frames-on-your-vsphere-esxi-box/</link>
				<pubDate>Tue, 02 Mar 2010 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2010/03/02/jumbo-frames-on-your-vsphere-esxi-box/</guid>
				<description>&lt;p&gt;Continuing on from this /2010/02/04/vsphere-and-multipathing-iscsi/&lt;/p&gt;&#xA;&lt;p&gt;you may want to implement jumbo frames to your iSCSI backend&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;Enable jumbo frames on your iSCSI target and switches then complete the following on the ESXi hosts (iSCSI initiators)&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;This to list your current switch details and port group names&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;esxcfg-vswitch -l&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;The following to allow jumbo frames onto your vswtich (insert your vSwich in following)&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;esxcfg-vswtich -m 9000 vSwitch0&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Then create your kernel port groups that you want to use for iscsi, my commands looked like this&amp;hellip; (repeat for each iscsi kernel port you have) &amp;ndash; note : DO NOT ADD ANY VMKERNEL(s) from the GUI, instead use the steps below&lt;/p&gt;</description>
			</item>
			<item>
				<title>vSphere and Multipathing iSCSI</title>
				<link>https://sigtar.com/2010/02/04/vsphere-and-multipathing-iscsi/</link>
				<pubDate>Thu, 04 Feb 2010 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2010/02/04/vsphere-and-multipathing-iscsi/</guid>
				<description>&lt;p&gt;This is just a quick reference to create a multiplathing iSCSI setup&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;Create two virtual kernel switches, one called &amp;ldquo;iSCSI-1&amp;rdquo; and the other called &amp;ldquo;iSCSI-2&amp;rdquo; (and so on if you have more nics)&lt;/p&gt;&#xA;&lt;p&gt;Then per kernel portgroup ensure that only one of the nics is active. For the &amp;ldquo;iSCSI-1&amp;rdquo; portgroup configure it to override the virtual switch settings and move nic 0 to active and nic 1 to &lt;strong&gt;unused&lt;/strong&gt;. For the &amp;ldquo;iSCSI-2&amp;rdquo; portgroup configure it to override the virtual switch settings and move nic 1 to active and nic 0 to &lt;strong&gt;unused&lt;/strong&gt;.&lt;/p&gt;</description>
			</item>
			<item>
				<title>HDD short stroking - is it worth it?</title>
				<link>https://sigtar.com/2009/12/21/hdd-short-stroking-is-it-worth-it/</link>
				<pubDate>Mon, 21 Dec 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/12/21/hdd-short-stroking-is-it-worth-it/</guid>
				<description>&lt;p&gt;I&amp;rsquo;ve got some old 250Gb drives that are starting to show their age. I&amp;rsquo;ve currently got them setup in a 3x RAID 0 config which presents about 750Gb of space.&lt;/p&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve got everything on a single partition (meh, i&amp;rsquo;m lazy). I&amp;rsquo;ve done various speed tests in the current setup (with all space allocated), but i thought i&amp;rsquo;d re-image onto a short stroke partition.&lt;/p&gt;&#xA;&lt;p&gt;I only use about 150Gb of space on my main machine (most of my data is on another box), so i&amp;rsquo;m going to try creating a 200Gb partition to test if this provides any kind of performance boost.&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>FreeNAS - zfs in version 0.7</title>
				<link>https://sigtar.com/2009/10/28/freenas-zfs-in-version-0-7/</link>
				<pubDate>Wed, 28 Oct 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/10/28/freenas-zfs-in-version-0-7/</guid>
				<description>&lt;p&gt;If you want to give zfs a go and also want a dedicated file server this is the solution.&lt;/p&gt;&#xA;&lt;p&gt;Check it out here;&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://www.freenas.org/&#34;&gt;http://www.freenas.org/&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://sigtar.com/wp-content/uploads/2009/10/smart.png&#34;&gt;&lt;img src=&#34;https://sigtar.com/wp-content/uploads/2009/10/smart.png&#34; alt=&#34;smart&#34; title=&#34;smart&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;I&amp;rsquo;m still using opensolaris though as i like running a few virtualbox machines on the same box.&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>zfs compression and latency</title>
				<link>https://sigtar.com/2009/08/19/zfs-compression-and-latency/</link>
				<pubDate>Wed, 19 Aug 2009 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2009/08/19/zfs-compression-and-latency/</guid>
				<description>&lt;p&gt;Since im using ZFS as storage via NFS for my some of my vmware environments i need to ensure that latency on my disk is reduced where ever possible.&lt;/p&gt;&#xA;&lt;p&gt;There is alot of talk about ZFS compression being &amp;ldquo;faster&amp;rdquo; than a non-compressed pool due to less physical data being pulled off the drives. This of course depends on the system powering ZFS, but i wanted to run some tests specifically on latency. Throughput is fine in some situations, but latency is a killer when it comes to lots of small reads and writes (in the case of hosting virtual machines)&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 : 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>
	</channel>
</rss>
