<?xml version='1.0' encoding='UTF-8'?>











<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
<title>Apple - Support - Most Popular  - Xsan</title>
<link>http://www.apple.com/support/</link>
<description>Apple - Support - Most Popular - Apple Inc.</description>
<language>en-us</language>
<copyright>Copyright 2013 Apple Inc.</copyright>
<ttl>1440</ttl>
<pubDate>Tue, 21 May 2013 19:13:06 GMT+00:00</pubDate>
<category>Apple</category>
<generator>In house</generator>
<docs>http://rss.support.apple.com/xsan/popular</docs>


					<item>
					<title><![CDATA[How to find your AppleCare registration number]]></title>
					<description><![CDATA[You'll need the AppleCare registration number to register a recently purchased AppleCare agreement if your agreement hasn't been registered yet.]]></description>
					<link>http://support.apple.com/kb/HT1863</link>
					<content:encoded><![CDATA[You'll need the AppleCare registration number to register a recently purchased AppleCare agreement if your agreement hasn't been registered yet.]]></content:encoded>
					<pubDate>Thu, 12 Jul 2012 03:16:37 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT1863</guid>
					</item>
					
					<item>
					<title><![CDATA[Promise VTrak: Configuring for optimal performance]]></title>
					<description><![CDATA[Configure Promise VTrak RAIDs for best performance using the guidelines in this article.]]></description>
					<link>http://support.apple.com/kb/HT1200</link>
					<content:encoded><![CDATA[Configure Promise VTrak RAIDs for best performance using the guidelines in this article.]]></content:encoded>
					<pubDate>Fri, 14 Sep 2012 18:13:11 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT1200</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan: Compatibility of SAN clients with Xsan and StorNext controllers]]></title>
					<description><![CDATA[Learn which versions of StorNext can be used in the same SAN with Xsan controllers, and which versions of Xsan can be used in the same SAN with StorNext controllers.]]></description>
					<link>http://support.apple.com/kb/HT1517</link>
					<content:encoded><![CDATA[Learn which versions of StorNext can be used in the same SAN with Xsan controllers, and which versions of Xsan can be used in the same SAN with StorNext controllers.]]></content:encoded>
					<pubDate>Mon, 20 May 2013 18:49:32 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT1517</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan: How to repair the filesystem]]></title>
					<description><![CDATA[Learn how to repair Xsan filesystems using cvfsck.]]></description>
					<link>http://support.apple.com/kb/HT1081</link>
					<content:encoded><![CDATA[Learn how to repair Xsan filesystems using cvfsck.]]></content:encoded>
					<pubDate>Fri, 14 Sep 2012 18:11:18 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT1081</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan: Cannot see or label LUNs during setup]]></title>
					<description><![CDATA[During setup, Xsan Admin may not show LUNs that were previously formatted for use with Mac OS Extended (also called HFS Plus, or HFS+) filesystems. This means they cannot be labeled as Xsan LUNs.]]></description>
					<link>http://support.apple.com/kb/TS1268</link>
					<content:encoded><![CDATA[During setup, Xsan Admin may not show LUNs that were previously formatted for use with Mac OS Extended (also called HFS Plus, or HFS+) filesystems. This means they cannot be labeled as Xsan LUNs.]]></content:encoded>
					<pubDate>Wed, 20 Jan 2010 15:18:45 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/TS1268</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan: Compatibility of Xsan versions with Mac OS X versions]]></title>
					<description><![CDATA[This article contains a list of which Xsan versions are compatible with which versions of Mac OS X client and server; the matrix shows required versions of Xsan and Mac OS X for when you want to upgrade your Xsan version. 
]]></description>
					<link>http://support.apple.com/kb/HT1862</link>
					<content:encoded><![CDATA[This article contains a list of which Xsan versions are compatible with which versions of Mac OS X client and server; the matrix shows required versions of Xsan and Mac OS X for when you want to upgrade your Xsan version. 
]]></content:encoded>
					<pubDate>Wed, 25 Jul 2012 20:16:34 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT1862</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan: Compatibility of Xsan metadata controllers (MDCs) and clients]]></title>
					<description><![CDATA[In some situations, you can use clients and metadata controllers with different versions of Xsan in the same SAN. In all cases, the versions of Xsan and Mac OS X on the metadata controller must the same as, or later than, the latest versions on a client.]]></description>
					<link>http://support.apple.com/kb/HT3755</link>
					<content:encoded><![CDATA[In some situations, you can use clients and metadata controllers with different versions of Xsan in the same SAN. In all cases, the versions of Xsan and Mac OS X on the metadata controller must the same as, or later than, the latest versions on a client.]]></content:encoded>
					<pubDate>Wed, 25 Jul 2012 20:17:18 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT3755</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan: Best practices for data integrity]]></title>
					<description><![CDATA[These suggested guidelines for deploying Xsan help to ensure consistent access to data stored on Xsan volumes.]]></description>
					<link>http://support.apple.com/kb/HT2761</link>
					<content:encoded><![CDATA[These suggested guidelines for deploying Xsan help to ensure consistent access to data stored on Xsan volumes.]]></content:encoded>
					<pubDate>Mon, 08 Jun 2009 14:42:03 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT2761</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan Help: Tips to avoid unexpected volume behavior]]></title>
					<description><![CDATA[Tips to avoid unexpected volume behavior.]]></description>
					<link>http://support.apple.com/kb/HT2784</link>
					<content:encoded><![CDATA[Tips to avoid unexpected volume behavior.]]></content:encoded>
					<pubDate>Tue, 11 Nov 2008 17:37:36 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT2784</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan: Guidelines for volume expansion]]></title>
					<description><![CDATA[When adding storage to an Xsan volume, use these guidelines.]]></description>
					<link>http://support.apple.com/kb/HT2769</link>
					<content:encoded><![CDATA[When adding storage to an Xsan volume, use these guidelines.]]></content:encoded>
					<pubDate>Wed, 30 Sep 2009 17:32:24 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT2769</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan: Manually configuring Xsan after promoting OS X Lion to Lion Server]]></title>
					<description><![CDATA[Learn how to manually set up Xsan on Lion Server after promoting the system from the OS&nbsp;X&nbsp;Lion (client).]]></description>
					<link>http://support.apple.com/kb/HT4782</link>
					<content:encoded><![CDATA[Learn how to manually set up Xsan on Lion Server after promoting the system from the OS&nbsp;X&nbsp;Lion (client).]]></content:encoded>
					<pubDate>Thu, 25 Aug 2011 15:54:10 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT4782</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan: "fsmpm not running" message in Xsan Admin]]></title>
					<description><![CDATA[Xsan Admin may display the message &quot;fsmpm not running&quot; for a computer that is a member of the Xsan.]]></description>
					<link>http://support.apple.com/kb/TS2923</link>
					<content:encoded><![CDATA[Xsan Admin may display the message &quot;fsmpm not running&quot; for a computer that is a member of the Xsan.]]></content:encoded>
					<pubDate>Mon, 20 Aug 2012 20:35:14 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/TS2923</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan 2: "The item will be deleted immediately" or "-1407" alert when moving items to the Trash]]></title>
					<description><![CDATA[When moving items from a locally-mounted Xsan volume to the Trash, you may see an alert stating &quot;The item will be deleted immediately&quot; or an alert with the number -1407.]]></description>
					<link>http://support.apple.com/kb/TS2942</link>
					<content:encoded><![CDATA[When moving items from a locally-mounted Xsan volume to the Trash, you may see an alert stating &quot;The item will be deleted immediately&quot; or an alert with the number -1407.]]></content:encoded>
					<pubDate>Mon, 14 Sep 2009 17:26:24 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/TS2942</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan: Some features are not supported with StorNext volumes]]></title>
					<description><![CDATA[Some Xsan features are not supported when accessing a SAN&nbsp;volume running on Quantum StorNext metadata controllers.]]></description>
					<link>http://support.apple.com/kb/HT3658</link>
					<content:encoded><![CDATA[Some Xsan features are not supported when accessing a SAN&nbsp;volume running on Quantum StorNext metadata controllers.]]></content:encoded>
					<pubDate>Fri, 14 Sep 2012 18:20:36 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT3658</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan 2: Compatibility of Xsan clients with Active Storage ActiveSAN shared storage systems]]></title>
					<description><![CDATA[Learn which versions of Xsan 2 are compatible with ActiveSAN shared storage systems.]]></description>
					<link>http://support.apple.com/kb/HT4944</link>
					<content:encoded><![CDATA[Learn which versions of Xsan 2 are compatible with ActiveSAN shared storage systems.]]></content:encoded>
					<pubDate>Fri, 23 Sep 2011 01:52:33 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT4944</guid>
					</item>
					
					<item>
					<title><![CDATA[Troubleshooting Xsan volume failover issues]]></title>
					<description><![CDATA[What is &quot;volume failover&quot;?
If two or more Metadata Controllers (MDC) are configured to host an Xsan volume, in the event that a MDC becomes inactive another MDC should take control of the Xsan volume. The act of a standby MDC assuming active hosting from another MDC is called &quot;failover.&quot;
Understanding failover-related communications:
While configuring Xsan, one designates over which subnet Xsan metadata communication will occur.&nbsp; Over this subnet, MDCs communicate failover-related heartbeats. If this heartbeat communication cannot occur due to network conditions or misconfiguration, failover will not occur as expected.
To determine which interface is being used for metadata communications follow these steps:
Xsan 2.0 and later:
Open Xsan Admin and select the Overview Pane. The Metadata Subnet is displayed in the Details section.
Xsan 1.4.2 and earlier:
Open Xsan Admin and select Setup &gt; Computers. Inspect the settings for each MDC. Observe the &lsquo;Access the SAN via&rsquo; setting which designates the subnet over which metadata communications will occur.
When may failover occur?
The following events may result in failover of all Xsan volumes:

    The active MDC is unreachable by the secondary MDC via the ethernet network used for metadata communications.
    The active MDC is rebooted or shutdown.

The following events will result in failover of a specific Xsan volume:

    The active MDC cannot see one or more LUNs associated with the volume.
    Xsan Admin or cvadmin is used to failover a volume.

Note: Following a failover event, a volume does not automatically failover back to the MDC that was hosting the volume previous to the failover.]]></description>
					<link>http://support.apple.com/kb/HT3315</link>
					<content:encoded><![CDATA[What is &quot;volume failover&quot;?
If two or more Metadata Controllers (MDC) are configured to host an Xsan volume, in the event that a MDC becomes inactive another MDC should take control of the Xsan volume. The act of a standby MDC assuming active hosting from another MDC is called &quot;failover.&quot;
Understanding failover-related communications:
While configuring Xsan, one designates over which subnet Xsan metadata communication will occur.&nbsp; Over this subnet, MDCs communicate failover-related heartbeats. If this heartbeat communication cannot occur due to network conditions or misconfiguration, failover will not occur as expected.
To determine which interface is being used for metadata communications follow these steps:
Xsan 2.0 and later:
Open Xsan Admin and select the Overview Pane. The Metadata Subnet is displayed in the Details section.
Xsan 1.4.2 and earlier:
Open Xsan Admin and select Setup &gt; Computers. Inspect the settings for each MDC. Observe the &lsquo;Access the SAN via&rsquo; setting which designates the subnet over which metadata communications will occur.
When may failover occur?
The following events may result in failover of all Xsan volumes:

    The active MDC is unreachable by the secondary MDC via the ethernet network used for metadata communications.
    The active MDC is rebooted or shutdown.

The following events will result in failover of a specific Xsan volume:

    The active MDC cannot see one or more LUNs associated with the volume.
    Xsan Admin or cvadmin is used to failover a volume.

Note: Following a failover event, a volume does not automatically failover back to the MDC that was hosting the volume previous to the failover.]]></content:encoded>
					<pubDate>Tue, 09 Feb 2010 16:38:48 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT3315</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan, Lion Server: Issues saving a file to an Xsan volume; "GSLibraryErrorDomain error 1" appears]]></title>
					<description><![CDATA[In OS X Lion and Lion Server v10.7 through v10.7.2, if a file on a locally mounted Xsan volume has been edited by multiple users on different systems, you may see the following alert message when trying to save the file:
&quot;The operation couldn&rsquo;t be completed. (GSLibraryErrorDomain error 1.)&quot;]]></description>
					<link>http://support.apple.com/kb/HT4762</link>
					<content:encoded><![CDATA[In OS X Lion and Lion Server v10.7 through v10.7.2, if a file on a locally mounted Xsan volume has been edited by multiple users on different systems, you may see the following alert message when trying to save the file:
&quot;The operation couldn&rsquo;t be completed. (GSLibraryErrorDomain error 1.)&quot;]]></content:encoded>
					<pubDate>Thu, 09 Feb 2012 18:00:22 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT4762</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan 2.2: How to set Spotlight search levels]]></title>
					<description><![CDATA[With Xsan 2.2, Spotlight supports two different levels of searching:&nbsp;File system search and Indexed search.

    File system search (FsSearch) - Searches against file system attributes are enabled but no indexed searching of content is performed.
    Indexed search (ReadWrite) - Full file system and indexed content is enabled; the index will be updated as file system content changes.

By default, Indexed search is enabled when Spotlight is activated for an Xsan volume in Xsan 2.0 or later.
The FsSearch option requires Mac OS&nbsp;X v10.6 metadata controllers using Xsan 2.2.]]></description>
					<link>http://support.apple.com/kb/HT3749</link>
					<content:encoded><![CDATA[With Xsan 2.2, Spotlight supports two different levels of searching:&nbsp;File system search and Indexed search.

    File system search (FsSearch) - Searches against file system attributes are enabled but no indexed searching of content is performed.
    Indexed search (ReadWrite) - Full file system and indexed content is enabled; the index will be updated as file system content changes.

By default, Indexed search is enabled when Spotlight is activated for an Xsan volume in Xsan 2.0 or later.
The FsSearch option requires Mac OS&nbsp;X v10.6 metadata controllers using Xsan 2.2.]]></content:encoded>
					<pubDate>Tue, 06 Oct 2009 19:51:19 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT3749</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan 2.x: If an Xsan volume failover occurs before Spotlight becomes active, the Backup Controller may not enable Spotlight]]></title>
					<description><![CDATA[After creating a volume with Spotlight enabled, or after enabling Spotlight on an Xsan volume, it make take several minutes for Spotlight to become active on the volume. &nbsp;During this time, if an MDC failover occurs, Spotlight will not activate properly. This article applies to Xsan v2.0 and later.]]></description>
					<link>http://support.apple.com/kb/TS2950</link>
					<content:encoded><![CDATA[After creating a volume with Spotlight enabled, or after enabling Spotlight on an Xsan volume, it make take several minutes for Spotlight to become active on the volume. &nbsp;During this time, if an MDC failover occurs, Spotlight will not activate properly. This article applies to Xsan v2.0 and later.]]></content:encoded>
					<pubDate>Fri, 05 Mar 2010 20:43:48 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/TS2950</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan 2 Administrator Guide v2.3: Revision to "Upgrade SAN hardware and software" procedure]]></title>
					<description><![CDATA[This document revises the &quot;Upgrade SAN hardware and software&quot; procedure on page 132 of the Xsan 2 Administrator Guide v2.3.]]></description>
					<link>http://support.apple.com/kb/HT5285</link>
					<content:encoded><![CDATA[This document revises the &quot;Upgrade SAN hardware and software&quot; procedure on page 132 of the Xsan 2 Administrator Guide v2.3.]]></content:encoded>
					<pubDate>Tue, 07 May 2013 19:18:19 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT5285</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan: Advanced options for mounting Xsan volumes]]></title>
					<description><![CDATA[There are several advanced command line options for controlling how Xsan volumes are mounted on Xsan clients. This article explains how to use the xsanctl command options.]]></description>
					<link>http://support.apple.com/kb/HT5187</link>
					<content:encoded><![CDATA[There are several advanced command line options for controlling how Xsan volumes are mounted on Xsan clients. This article explains how to use the xsanctl command options.]]></content:encoded>
					<pubDate>Fri, 05 Oct 2012 21:50:28 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT5187</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan 2: Compatibility of Xsan clients with Grass Valley SAN shared storage systems]]></title>
					<description><![CDATA[Learn which versions of Xsan 2 are compatible with Grass Valley SAN shared storage systems.]]></description>
					<link>http://support.apple.com/kb/HT3531</link>
					<content:encoded><![CDATA[Learn which versions of Xsan 2 are compatible with Grass Valley SAN shared storage systems.]]></content:encoded>
					<pubDate>Thu, 25 Aug 2011 20:03:31 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT3531</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan volume may not mount, fsmpm may not run after migrating from Mac OS X v10.6 to OS X Lion]]></title>
					<description><![CDATA[Xsan may need to be enabled on OS&nbsp;X&nbsp;Lion clients that were migrated from Mac OS&nbsp;X&nbsp;v10.6 via the Migration Assistant. A migrated system may show fsmpm's status as not running, or may show the computer as unreachable or offline in Xsan Admin on another system such as the metadata controller.]]></description>
					<link>http://support.apple.com/kb/HT4801</link>
					<content:encoded><![CDATA[Xsan may need to be enabled on OS&nbsp;X&nbsp;Lion clients that were migrated from Mac OS&nbsp;X&nbsp;v10.6 via the Migration Assistant. A migrated system may show fsmpm's status as not running, or may show the computer as unreachable or offline in Xsan Admin on another system such as the metadata controller.]]></content:encoded>
					<pubDate>Wed, 20 Jul 2011 22:57:13 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT4801</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan: Unable to enable case insensitivity on a volume]]></title>
					<description><![CDATA[Xsan 2.3 introduces the ability to create case insensitive volumes. You can also change case sensitivity after you create a volume.]]></description>
					<link>http://support.apple.com/kb/HT4793</link>
					<content:encoded><![CDATA[Xsan 2.3 introduces the ability to create case insensitive volumes. You can also change case sensitivity after you create a volume.]]></content:encoded>
					<pubDate>Wed, 15 Aug 2012 20:28:24 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT4793</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan: Enable RPL on StorNext volumes running on StorNext 4 MDCs]]></title>
					<description><![CDATA[StorNext volumes accessed by Xsan clients running OS&nbsp;X&nbsp;Lion and Mountain Lion need fast reverse path lookup (RPL)&nbsp;enabled. Learn how to enable RPL&nbsp;with the steps in this article.]]></description>
					<link>http://support.apple.com/kb/HT5611</link>
					<content:encoded><![CDATA[StorNext volumes accessed by Xsan clients running OS&nbsp;X&nbsp;Lion and Mountain Lion need fast reverse path lookup (RPL)&nbsp;enabled. Learn how to enable RPL&nbsp;with the steps in this article.]]></content:encoded>
					<pubDate>Wed, 09 Jan 2013 19:37:54 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT5611</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan: How to defragment data for multimedia applications]]></title>
					<description><![CDATA[If you have media or render files stored on an Xsan volume that have become fragmented, multimedia applications may report dropped frames when you work with them. This can occur with any version of Final Cut Pro, Final Cut Express, iMovie, and Xsan.]]></description>
					<link>http://support.apple.com/kb/TS2778</link>
					<content:encoded><![CDATA[If you have media or render files stored on an Xsan volume that have become fragmented, multimedia applications may report dropped frames when you work with them. This can occur with any version of Final Cut Pro, Final Cut Express, iMovie, and Xsan.]]></content:encoded>
					<pubDate>Thu, 04 Jun 2009 14:39:06 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/TS2778</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan 2.3: Update to StorNext SNFS v4.2.1 controller to avoid data loss issue]]></title>
					<description><![CDATA[Xsan 2.3 clients (running OS&nbsp;X&nbsp;Lion or Lion Server v10.7.2 or earlier) that access filesystems hosted by controllers that use StorNext SNFS version 4.2.0 may experience data loss when renaming files on StorNext-hosted volumes.
A file may be unexpectedly deleted when renamed to a new name which differs only in the capitalization of the letters; for example, when changing &quot;test&quot; to &quot;TEST&quot;.]]></description>
					<link>http://support.apple.com/kb/TS4171</link>
					<content:encoded><![CDATA[Xsan 2.3 clients (running OS&nbsp;X&nbsp;Lion or Lion Server v10.7.2 or earlier) that access filesystems hosted by controllers that use StorNext SNFS version 4.2.0 may experience data loss when renaming files on StorNext-hosted volumes.
A file may be unexpectedly deleted when renamed to a new name which differs only in the capitalization of the letters; for example, when changing &quot;test&quot; to &quot;TEST&quot;.]]></content:encoded>
					<pubDate>Fri, 20 Jan 2012 18:05:30 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/TS4171</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan 2.3: Deactivating a storage pool]]></title>
					<description><![CDATA[It may be necessary to deactivate (down) an Xsan data storage pool in a volume, but retain access to data on other storage pools within the volume. You may need to do this if there is a LUN issue in an Xsan storage pool  and Xsan clients are unable to mount the Xsan volume, for example.]]></description>
					<link>http://support.apple.com/kb/HT4656</link>
					<content:encoded><![CDATA[It may be necessary to deactivate (down) an Xsan data storage pool in a volume, but retain access to data on other storage pools within the volume. You may need to do this if there is a LUN issue in an Xsan storage pool  and Xsan clients are unable to mount the Xsan volume, for example.]]></content:encoded>
					<pubDate>Wed, 20 Jul 2011 22:39:16 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT4656</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan, Lion Server: Use case sensitive volumes for StorNext and pre-Lion clients]]></title>
					<description><![CDATA[With Lion Server, Xsan adds case insensitivity. New volumes are case insensitive by default. You can set a volume to be case sensitive or insensitive by   changing the volume settings in XsanAdmin.]]></description>
					<link>http://support.apple.com/kb/HT4683</link>
					<content:encoded><![CDATA[With Lion Server, Xsan adds case insensitivity. New volumes are case insensitive by default. You can set a volume to be case sensitive or insensitive by   changing the volume settings in XsanAdmin.]]></content:encoded>
					<pubDate>Wed, 20 Jul 2011 22:40:31 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT4683</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan 2.2: Long DNS names may cause Xsan volume failover]]></title>
					<description><![CDATA[An Xsan volume may failover unexpectedly at the beginning of each hour (when summary statistics are written to the Xsan volume log) if any Xsan client of the volume has a very long DNS name.]]></description>
					<link>http://support.apple.com/kb/TS3328</link>
					<content:encoded><![CDATA[An Xsan volume may failover unexpectedly at the beginning of each hour (when summary statistics are written to the Xsan volume log) if any Xsan client of the volume has a very long DNS name.]]></content:encoded>
					<pubDate>Thu, 25 Aug 2011 21:37:28 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/TS3328</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan 2.2: Windows client unable to copy item from share point via SMB when native extended attributes are enabled]]></title>
					<description><![CDATA[With Xsan 2.2 or later, Xsan volumes can be created or updated to use native extended attributes.
If native extended attributes have been implemented on an Xsan volume, Windows users connecting over SMB may receive a message stating that an item can't be copied from the share point because the item can't be found.]]></description>
					<link>http://support.apple.com/kb/TS3179</link>
					<content:encoded><![CDATA[With Xsan 2.2 or later, Xsan volumes can be created or updated to use native extended attributes.
If native extended attributes have been implemented on an Xsan volume, Windows users connecting over SMB may receive a message stating that an item can't be copied from the share point because the item can't be found.]]></content:encoded>
					<pubDate>Wed, 06 Jan 2010 02:34:33 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/TS3179</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan: Troubleshooting "Disk Stripe Group DOWN for this client" errors]]></title>
					<description><![CDATA[
    An Xsan metadata controller's system log may show repeating messages similar to the following:
    
Aug 25 08:37:12 mdc1 fsm[123]: Xsan FSS 'MyVolume[0]': [Node 42] Disk Stripe Group 1 is DOWN for this client. # disks 2 unitmap[1] 0xfffff partaccess 0x1
    
    Xsan Admin may report that there are no visible LUNs for an Xsan client.
    Attempting to mount a volume in Xsan Admin may not work, and this alert may appear: &quot;Not all data LUNs of the volume are visible to this computer. Check the Fibre Channel cables and try again.&quot;
]]></description>
					<link>http://support.apple.com/kb/TS3480</link>
					<content:encoded><![CDATA[
    An Xsan metadata controller's system log may show repeating messages similar to the following:
    
Aug 25 08:37:12 mdc1 fsm[123]: Xsan FSS 'MyVolume[0]': [Node 42] Disk Stripe Group 1 is DOWN for this client. # disks 2 unitmap[1] 0xfffff partaccess 0x1
    
    Xsan Admin may report that there are no visible LUNs for an Xsan client.
    Attempting to mount a volume in Xsan Admin may not work, and this alert may appear: &quot;Not all data LUNs of the volume are visible to this computer. Check the Fibre Channel cables and try again.&quot;
]]></content:encoded>
					<pubDate>Wed, 01 Sep 2010 21:50:07 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/TS3480</guid>
					</item>
					
					<item>
					<title><![CDATA[Update Xsan 2.1.1 to 2.2 for compatibility with Mac OS X v10.6 or Mac OS X Server v10.6]]></title>
					<description><![CDATA[Xsan 2.1.1 is not compatible with Mac OS X v10.6 or Mac OS X Server v10.6 Snow Leopard.]]></description>
					<link>http://support.apple.com/kb/HT3826</link>
					<content:encoded><![CDATA[Xsan 2.1.1 is not compatible with Mac OS X v10.6 or Mac OS X Server v10.6 Snow Leopard.]]></content:encoded>
					<pubDate>Mon, 14 Sep 2009 17:33:21 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT3826</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan: Install Xsan 2.2 Update for 10.6 after installing Mac OS X v10.6]]></title>
					<description><![CDATA[After upgrading an Xsan system to Mac OS&nbsp;X v10.6 Snow Leopard or Mac OS&nbsp;X&nbsp;Server v10.6, you may see one of these status messages&nbsp; in the Xsan Admin computer list next to the Mac that was upgraded:

    &quot;Xsan 2 not installed&quot;
    &quot;Unreachable or offline&quot;
]]></description>
					<link>http://support.apple.com/kb/TS2920</link>
					<content:encoded><![CDATA[After upgrading an Xsan system to Mac OS&nbsp;X v10.6 Snow Leopard or Mac OS&nbsp;X&nbsp;Server v10.6, you may see one of these status messages&nbsp; in the Xsan Admin computer list next to the Mac that was upgraded:

    &quot;Xsan 2 not installed&quot;
    &quot;Unreachable or offline&quot;
]]></content:encoded>
					<pubDate>Tue, 03 Nov 2009 00:23:12 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/TS2920</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan 2: Optimizing file system journal size]]></title>
					<description><![CDATA[Xsan versions earlier than 2.2 defaulted to creating a file system journal of 16 MB, which is a reasonable default for many Xsan volumes. There may be circumstances in which this journal size may be insufficient and hamper performance in file system operations, especially ones involving metadata. Increasing the journal size may improve performance of file system operations. Changing the journal size for an Xsan volume can be done without recreating the volume. You should first back up your Xsan configuration on your metadata controllers, back up any data, and test the changes in a test environment before implementing them in a production environment.
Xsan 2.2 automatically includes this change in the volume Journal when the volume is created, but this process will still be valid if you wish to manually tune the journal size.]]></description>
					<link>http://support.apple.com/kb/HT3762</link>
					<content:encoded><![CDATA[Xsan versions earlier than 2.2 defaulted to creating a file system journal of 16 MB, which is a reasonable default for many Xsan volumes. There may be circumstances in which this journal size may be insufficient and hamper performance in file system operations, especially ones involving metadata. Increasing the journal size may improve performance of file system operations. Changing the journal size for an Xsan volume can be done without recreating the volume. You should first back up your Xsan configuration on your metadata controllers, back up any data, and test the changes in a test environment before implementing them in a production environment.
Xsan 2.2 automatically includes this change in the volume Journal when the volume is created, but this process will still be valid if you wish to manually tune the journal size.]]></content:encoded>
					<pubDate>Mon, 14 Sep 2009 17:27:19 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT3762</guid>
					</item>
					
					<item>
					<title><![CDATA[Promise VTrak: Fourth SAS-connected Expansion Chassis Only: Xsan (Data Only) configuration script]]></title>
					<description><![CDATA[This article contains a script used to configure Promise VTrak SAS-connected Expansion Chassis for Xsan. This script is used in the event that a Promise VTrak RAID Controller has already been configured for use with Xsan, and that an Expansion Chassis is being connected to the already-configured RAID Controller.]]></description>
					<link>http://support.apple.com/kb/HT3602</link>
					<content:encoded><![CDATA[This article contains a script used to configure Promise VTrak SAS-connected Expansion Chassis for Xsan. This script is used in the event that a Promise VTrak RAID Controller has already been configured for use with Xsan, and that an Expansion Chassis is being connected to the already-configured RAID Controller.]]></content:encoded>
					<pubDate>Tue, 15 May 2012 22:23:38 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT3602</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan: Finder states "backup items can't be modified" when moving items to Trash on StorNext volume]]></title>
					<description><![CDATA[Xsan users may see the following alert message in the Finder when dragging files from StorNext volumes to the Trash:
&quot;The operation can't be completed because backup items can't be modified.&quot;
This issue may occur on volumes controlled by StorNext 4.x metadata  controllers when the fast reverse path lookup (RPL)&nbsp;feature is disabled  on the volume.]]></description>
					<link>http://support.apple.com/kb/TS4501</link>
					<content:encoded><![CDATA[Xsan users may see the following alert message in the Finder when dragging files from StorNext volumes to the Trash:
&quot;The operation can't be completed because backup items can't be modified.&quot;
This issue may occur on volumes controlled by StorNext 4.x metadata  controllers when the fast reverse path lookup (RPL)&nbsp;feature is disabled  on the volume.]]></content:encoded>
					<pubDate>Thu, 20 Dec 2012 18:05:27 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/TS4501</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan: Ensuring that files or folders go to the intended affinities]]></title>
					<description><![CDATA[In order to force a file to relocate to the storage pool(s) specified by a folder's affinity, the file must be physically copied or re-written, not copied via the Finder or via a mv command.
]]></description>
					<link>http://support.apple.com/kb/HT4143</link>
					<content:encoded><![CDATA[In order to force a file to relocate to the storage pool(s) specified by a folder's affinity, the file must be physically copied or re-written, not copied via the Finder or via a mv command.
]]></content:encoded>
					<pubDate>Fri, 30 Apr 2010 15:22:22 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT4143</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan 2.2: Ex30 ALUA settings may interfere with Xsan Admin on Snow Leopard computers]]></title>
					<description><![CDATA[If asymmetric logical unit access (ALUA) is enabled on Promise VTrak Ex30 controllers and you are using Snow Leopard based Xsan controllers or clients, Xsan Admin may not be able to connect the Xsan environment.

The primary symptom is that Xsan Admin may not be able to connect to servermgrd. These messages may appear in the system.log of the Xsan controller or client:
&nbsp;
&nbsp;&nbsp; &nbsp;timestamp hostname servermgrd[59068]: requests = (\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Command = getComputerProperties;\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Module = &quot;servermgr_xsan&quot;;\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Timestamp = &quot;2011-07-16 11:08:09 -0700&quot;;\n&nbsp;&nbsp;&nbsp; },\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Command = getComputerProperties;\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Module = &quot;servermgr_xsan&quot;;\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Timestamp = &quot;2011-07-16 11:08:31 -0700&quot;;\n&nbsp;&nbsp;&nbsp; },\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Command = Idle;\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Module = &quot;servermgr_xsan&quot;;\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Timestamp = &quot;2011-07-16 11:08:45 -0700&quot;;\n&nbsp;&nbsp;&nbsp; }\n)
&nbsp;&nbsp; &nbsp;timestamp hostname servermgrd[59068]: [59068] error in getAndLockContext: flock(servermgr_xsan) FATAL time out

Other symptoms may include cvlabel taking several minutes to run instead of a few seconds. When this occurs, there may also be duplicate LUN serial numbers displayed with different attributes, such as sector count and size, but the same serial number:

&nbsp;&nbsp; &nbsp;CvfsDisk_UNKNOWN /dev/rdisk75&nbsp;&nbsp;&nbsp; # host 1 lun 6 sectors 23437479903 sector_size 512 inquiry [Promise VTrak E630 1007] serial 2231000155498DB5
&nbsp;&nbsp; &nbsp;CvfsDisk_UNKNOWN /dev/rdisk97&nbsp;&nbsp;&nbsp; # host 2 lun 6 sectors 0 sector_size 0 inquiry [Promise VTrak E630 1007] serial 2231000155498DB5 [Unusable: Unable to read label]]]></description>
					<link>http://support.apple.com/kb/TS3905</link>
					<content:encoded><![CDATA[If asymmetric logical unit access (ALUA) is enabled on Promise VTrak Ex30 controllers and you are using Snow Leopard based Xsan controllers or clients, Xsan Admin may not be able to connect the Xsan environment.

The primary symptom is that Xsan Admin may not be able to connect to servermgrd. These messages may appear in the system.log of the Xsan controller or client:
&nbsp;
&nbsp;&nbsp; &nbsp;timestamp hostname servermgrd[59068]: requests = (\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Command = getComputerProperties;\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Module = &quot;servermgr_xsan&quot;;\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Timestamp = &quot;2011-07-16 11:08:09 -0700&quot;;\n&nbsp;&nbsp;&nbsp; },\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Command = getComputerProperties;\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Module = &quot;servermgr_xsan&quot;;\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Timestamp = &quot;2011-07-16 11:08:31 -0700&quot;;\n&nbsp;&nbsp;&nbsp; },\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Command = Idle;\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Module = &quot;servermgr_xsan&quot;;\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Timestamp = &quot;2011-07-16 11:08:45 -0700&quot;;\n&nbsp;&nbsp;&nbsp; }\n)
&nbsp;&nbsp; &nbsp;timestamp hostname servermgrd[59068]: [59068] error in getAndLockContext: flock(servermgr_xsan) FATAL time out

Other symptoms may include cvlabel taking several minutes to run instead of a few seconds. When this occurs, there may also be duplicate LUN serial numbers displayed with different attributes, such as sector count and size, but the same serial number:

&nbsp;&nbsp; &nbsp;CvfsDisk_UNKNOWN /dev/rdisk75&nbsp;&nbsp;&nbsp; # host 1 lun 6 sectors 23437479903 sector_size 512 inquiry [Promise VTrak E630 1007] serial 2231000155498DB5
&nbsp;&nbsp; &nbsp;CvfsDisk_UNKNOWN /dev/rdisk97&nbsp;&nbsp;&nbsp; # host 2 lun 6 sectors 0 sector_size 0 inquiry [Promise VTrak E630 1007] serial 2231000155498DB5 [Unusable: Unable to read label]]]></content:encoded>
					<pubDate>Fri, 22 Jul 2011 17:59:23 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/TS3905</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan 2.x: Populating Xsan Admin's serial number list by use of a text file or copy/paste]]></title>
					<description><![CDATA[Xsan Admin 2 lets you easily populate the serial number list by dragging a text document's list of serial numbers to Xsan Admin, or by copying and pasting a list of serial numbers from a document or email message.]]></description>
					<link>http://support.apple.com/kb/HT4391</link>
					<content:encoded><![CDATA[Xsan Admin 2 lets you easily populate the serial number list by dragging a text document's list of serial numbers to Xsan Admin, or by copying and pasting a list of serial numbers from a document or email message.]]></content:encoded>
					<pubDate>Thu, 14 Oct 2010 23:05:54 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT4391</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan 2.x: Available free space incorrect after bandwidth expansion]]></title>
					<description><![CDATA[After expanding an Xsan volume,  the available free space may be less than expected. If free space does not increase by the size of the storage that was added to the volume, follow the instructions in this article.]]></description>
					<link>http://support.apple.com/kb/TS3041</link>
					<content:encoded><![CDATA[After expanding an Xsan volume,  the available free space may be less than expected. If free space does not increase by the size of the storage that was added to the volume, follow the instructions in this article.]]></content:encoded>
					<pubDate>Fri, 02 Oct 2009 16:13:11 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/TS3041</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan Admin 2.2: Xsan Admin recommends Xsan 2.2.1 for Mac Pro with update]]></title>
					<description><![CDATA[After you upgrade your Mac Pro (Mid 2010) to Xsan 2.2.1, Xsan Admin 2.2 may display the status warning message &quot;Xsan 2.2.1 recommended&quot;.]]></description>
					<link>http://support.apple.com/kb/TS3440</link>
					<content:encoded><![CDATA[After you upgrade your Mac Pro (Mid 2010) to Xsan 2.2.1, Xsan Admin 2.2 may display the status warning message &quot;Xsan 2.2.1 recommended&quot;.]]></content:encoded>
					<pubDate>Mon, 16 Aug 2010 15:19:29 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/TS3440</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan 2: Xsan Admin displays an authentication alert if HTTPS proxy is used]]></title>
					<description><![CDATA[When using Xsan Admin on a Mac that has been configured to use an HTTPS proxy, you may encounter unexpected authentication issues when connecting to Xsan systems. The following alert may appear:
&quot;Authentication failures occurred. Not all clients were successfully authenticated.&quot;]]></description>
					<link>http://support.apple.com/kb/TS4277</link>
					<content:encoded><![CDATA[When using Xsan Admin on a Mac that has been configured to use an HTTPS proxy, you may encounter unexpected authentication issues when connecting to Xsan systems. The following alert may appear:
&quot;Authentication failures occurred. Not all clients were successfully authenticated.&quot;]]></content:encoded>
					<pubDate>Fri, 18 May 2012 19:35:56 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/TS4277</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan: "File System is exposed to Product Alert 35" when running cvfsck]]></title>
					<description><![CDATA[In some rare situations, you might receive the following alert when running cvfsck on a StorNext hosted volume:
&nbsp;
&quot;File system is exposed to Product Alert 35. Please check AppleCare's web site at http://www.apple.com/support/xsan for more information.&quot;]]></description>
					<link>http://support.apple.com/kb/TS3900</link>
					<content:encoded><![CDATA[In some rare situations, you might receive the following alert when running cvfsck on a StorNext hosted volume:
&nbsp;
&quot;File system is exposed to Product Alert 35. Please check AppleCare's web site at http://www.apple.com/support/xsan for more information.&quot;]]></content:encoded>
					<pubDate>Fri, 29 Jul 2011 17:15:11 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/TS3900</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan 2.2 or later: Use same native extended attributes setting when multiple Xsan volumes are in use]]></title>
					<description><![CDATA[When ACLs are in use, copying files from an Xsan volume with native extended attributes enabled, to an Xsan volume without native extended attributes enabled, can result in the creation of AppleDouble files that do not have the intended ACLs. This can result in unexpected behavior when attempting to manipulate files with extended attributes.]]></description>
					<link>http://support.apple.com/kb/TS3344</link>
					<content:encoded><![CDATA[When ACLs are in use, copying files from an Xsan volume with native extended attributes enabled, to an Xsan volume without native extended attributes enabled, can result in the creation of AppleDouble files that do not have the intended ACLs. This can result in unexpected behavior when attempting to manipulate files with extended attributes.]]></content:encoded>
					<pubDate>Mon, 13 Sep 2010 18:57:22 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/TS3344</guid>
					</item>
					
					<item>
					<title><![CDATA[Promise VTrak: RAID Head - Xsan (Metadata, Journal, and Data)]]></title>
					<description><![CDATA[This article contains a script used to configure Promise VTrak RAID&nbsp;controllers for Xsan (Metadata, Journal, and Data).]]></description>
					<link>http://support.apple.com/kb/HT4693</link>
					<content:encoded><![CDATA[This article contains a script used to configure Promise VTrak RAID&nbsp;controllers for Xsan (Metadata, Journal, and Data).]]></content:encoded>
					<pubDate>Thu, 05 Jul 2012 20:42:32 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT4693</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan 2.2: Avoid using native extended attributes with StorNext clients]]></title>
					<description><![CDATA[If you connect StorNext clients to your SAN running Xsan 2.2, avoid using native extended attributes. StorNext clients will not preserve extended attributes when copying or moving files on the Xsan 2.2 volume.]]></description>
					<link>http://support.apple.com/kb/HT3751</link>
					<content:encoded><![CDATA[If you connect StorNext clients to your SAN running Xsan 2.2, avoid using native extended attributes. StorNext clients will not preserve extended attributes when copying or moving files on the Xsan 2.2 volume.]]></content:encoded>
					<pubDate>Mon, 14 Sep 2009 17:28:16 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT3751</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan 2.2: "Incorrect search policy" appears in Xsan Admin]]></title>
					<description><![CDATA[In Xsan Admin 2.2, computers may be reported as having an &quot;Incorrect search policy&quot; if the Directory Service search policy on the Xsan node is changed. 
If Xsan manages your users and groups, or if you chose to connect to an existing Open Directory domain in Server Assistant, then Xsan Admin will monitor the Directory Service search policy on each Xsan node. In these two situations, Xsan Admin expects each nodes' search policy to contain only the server(s) that Xsan Admin adds to the computers.]]></description>
					<link>http://support.apple.com/kb/HT3888</link>
					<content:encoded><![CDATA[In Xsan Admin 2.2, computers may be reported as having an &quot;Incorrect search policy&quot; if the Directory Service search policy on the Xsan node is changed. 
If Xsan manages your users and groups, or if you chose to connect to an existing Open Directory domain in Server Assistant, then Xsan Admin will monitor the Directory Service search policy on each Xsan node. In these two situations, Xsan Admin expects each nodes' search policy to contain only the server(s) that Xsan Admin adds to the computers.]]></content:encoded>
					<pubDate>Tue, 13 Oct 2009 20:43:59 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT3888</guid>
					</item>
					
					<item>
					<title><![CDATA[Promise VTrak: RAID Controllers and SAS-connected Expansion Chassis: Xsan (Metadata, Journal and Data)]]></title>
					<description><![CDATA[This article contains a script used to configure Promise VTrak RAID controllers with SAS-connected Expansion Chassis for Xsan (Metadata, Journal, and Data).]]></description>
					<link>http://support.apple.com/kb/HT4694</link>
					<content:encoded><![CDATA[This article contains a script used to configure Promise VTrak RAID controllers with SAS-connected Expansion Chassis for Xsan (Metadata, Journal, and Data).]]></content:encoded>
					<pubDate>Thu, 05 Jul 2012 20:40:37 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/HT4694</guid>
					</item>
					
					<item>
					<title><![CDATA[Xsan Admin displays incorrect "Volume is not running" alert after upgrading Xsan metadata controllers to Lion]]></title>
					<description><![CDATA[After upgrading an Xsan metadata controller (MDC) from Mac OS&nbsp;X&nbsp;v10.6 Snow Leopard to OS&nbsp;X Lion, Xsan Admin may display a warning triangle over an Xsan volume. Hovering the mouse pointer over the warning triangle reveals the following alert:
&quot;Volume is not running on mdc2.example.com&quot;
This message appears even though there is an fsm process for the volume running on the MDC named in the message.]]></description>
					<link>http://support.apple.com/kb/TS4481</link>
					<content:encoded><![CDATA[After upgrading an Xsan metadata controller (MDC) from Mac OS&nbsp;X&nbsp;v10.6 Snow Leopard to OS&nbsp;X Lion, Xsan Admin may display a warning triangle over an Xsan volume. Hovering the mouse pointer over the warning triangle reveals the following alert:
&quot;Volume is not running on mdc2.example.com&quot;
This message appears even though there is an fsm process for the volume running on the MDC named in the message.]]></content:encoded>
					<pubDate>Tue, 04 Dec 2012 16:55:36 GMT+00:00</pubDate>
					<guid>http://support.apple.com/kb/TS4481</guid>
					</item>
					
</channel>
</rss>

