Sun's ZFS now has built-in deduplication A few years ago, Deduplication was the industries biggest buzz word. Well that hype actually pan-out and is a vital way to save disk space. In a nutshell, Deduplication is the process of eliminating duplicate...
Windows XP Freezes There are many reasons why Windows XP freezes. One of the reasons may be that the registry is polluted with errors, or it is likely that your computer is bogged down by temporary Internet files. Having...
After carving up a Clariion lun to one of my sun servers. I tried to add it to Veritas but it kept failing with an error similar to
root:dwhdev2 :[/root] vxdisk -f init c#t#d3
VxVM vxdisk ERROR V-5-1-5433 Device c#t#d3: init failed:
Disk VTOC does not list private partition
Written by diwakarnitw on Jul-22-07
From: storageknowledgeshare.blogspot.com
What are the differences between failover modes on a CLARiiON array?
A CLARiiON array is an Active/Passive device and uses a LUN ownership model. In other words, when a LUN is bound it has a default owner, either SP-A or SP-B. I/O requests traveling to a port SP-A can only reach LUNs owned by SP-A and I/O requests traveling to a port on SP-B can only reach LUNs owned SP-B. It is necessary to have different failover methods because in certain situations a host will need to access a LUN on the non-owning SP.
The following failover modes apply:
Failover Mode 0 –
LUN Based Trespass Mode This failover mode is the default and works in conjunction with the Auto-trespass feature. Auto-trespass is a mode of operation that is set on a LUN by LUN basis. If Auto-Trespass is enabled on the LUN, the non-owning SP will report that the LUN exists and is available for access. The LUN will trespass to the SP where the I/O request is sent. Every time the LUN is trespassed a Unit Attention message is recorded. If Auto-trespass is disabled, the non-owning SP will report that the LUN exists but it is not available for access. If an I/O request is sent to the non-owning SP, it is rejected and the LUN’s ownership will not change. Note: The combination of Failover Mode 0 and Auto-Trespass can be dangerous if the host is sending I/O requests to both SP-A and SP-B because the LUN will need to trespass to fulfill each request. This combination is most commonly seen on an HP-UX server using PV-Links. The Auto-trespass feature is enabled through the Initiator Type setting of HP-AutoTrespass. A host with no failover software should use the combination of Failover Mode 0 and Auto-trespass disabled.
