Apple Xsan 2 - Manual (Page 131)

Appendix A Upgrade to Xsan 2.3 131
Upgrading to Mac OS X Lion or Lion Server upgrades Xsan to version 2.3.
If SAN volumes don’t mount on a client upgraded to Mac OS X Lion or Lion Server, use
the Xsan pane of System Preferences on the client to make sure Xsan is enabled.
Upgrade Xsan only:
On a client computer with Mac OS X or Mac OS X Server v10.6, choose Software
m
Update from the Apple menu and update to Xsan 2.2.1 or later.
If the client computer has Mac OS X or Mac OS X Server v10.5 or earlier, you must
upgrade it to v10.6 in order to use it in your Xsan 2.3 SAN.
If Xsan Admin displays a message about “Incorrect Search Policy,” use the Login
Options section of the Users & Groups pane of System Preferences (the Accounts pane
in Mac OS X v10.6) to connect to the correct network account server (directory server).
Step 7: Enable extended attributes
If you have only Macs on your SAN, enable extended attributes on your SAN volumes
to improve volume performance and efficiency.
Important: Enabling extended attributes can’t be undone.
WARNING: To avoid data loss, clients with Quantum’s StorNext File System (Windows,
AIX, IRIX, Linux, and Solaris computers) must not access volumes that use extended
attributes.
Enable extended attributes:
1 Open Xsan Admin and select Volumes in the SAN Assets list.
2 Select the volume and choose Edit Volume Settings from the Action pop-up menu (gear).
3 Click to select “Enable on this volume” next to Extended Attributes.
The time it takes to convert the volume to use extended attributes depends on
the number of files on the volume—it might take several hours for a large volume.
During this time, the volume is mounted only on the converting controller and can’t
be used by clients. The volume is mounted on clients and other controllers when the
conversion is finished.
Step 8: Change filename case sensitivity
If all your SAN computers have Mac OS X Lion or Lion Server, you can specify whether
a volume ignores capitalization in filenames. For example, a volume can consider
myfile, MyFile, and MYFILE to be the same or different filenames.
For best performance with volumes that you share using the SMB protocol, make them
case insensitive.