User guide

Chapter 4 Managing SAN Storage 61
Enabling Extended Attributes
If all computers on your SAN are running Xsan 2.2, you can enable extended attributes
for the les on your volumes. When extended attributes are enabled, attributes
associated with a le are stored inside the le itself rather than in separate hidden les.
Enabling extended attributes improves le system performance.
Important: You can’t disable extended attributes. Enabling them on a volume is a
one-way process and can’t be undone.
To enable extended attributes:
1 In Xsan Admin, select Volumes in the SAN Assets list.
2 Select the volume and choose Edit Volume Settings from the Action (gear) pop-up
menu.
3 Select the checkbox next to Extended Attributes and click OK.
The time needed to convert the volume to use extended attributes depends on the
size of the volume and the number of les stored on it.
Enabling or Disabling Access Control Lists
You can use Xsan Admin to specify whether the Xsan le system uses access control
lists (ACLs) on a volume.
Xsan 2 clients and Windows StorNext clients recognize ACLs. UNIX clients ignore ACLs
on Xsan volumes. If you have a mix of Windows clients and Xsan clients, they must
all be bound to the same directory domain, whether provided by Open Directory
congured as a primary domain controller (PDC) or by Windows Active Directory.
Note: If you enable ACLs but your SAN includes clients that don’t support them, don’t
use those clients to change le or folder ownership information, or inconsistencies
might result.
To enable or disable ACLs:
1 In Xsan Admin, select Volumes in the SAN Assets list.
2 Select the volume and choose Edit Volume Settings from the Action (gear) pop-up
menu.
3 Set or clear the checkbox next to Access Control Lists and click OK.
Changing the Windows ID Mapping
If you have Windows clients on your SAN, the Windows ID Mapping setting determines
how they map user and group information to the Xsan-compatible user IDs and group
IDs they need in order to access this volume. For more information, see “Mapping
Windows User and Group IDs” on page 78.