Change volume settings

You can use Server to specify whether the Xsan file system uses access control lists (ACLs) on a volume.

Xsan 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.

1. In the Xsan pane of the Server app, select the volume you want to edit.

2. Click the Action pop-up menu , then choose Edit Volume.

3. Select “Use access control lists,” then click OK.

   After you click OK, the volume is unmounted from all SAN computers, then remounted.

You can specify whether a volume notices capitalization in filenames. For example, a volume can consider myfile, MyFile, and MYFILE to be the same or different filenames.

If “Use case sensitive file system” isn’t selected, the volume considers filenames to be the same if they’re spelled alike but capitalized differently.

If “Use case sensitive file system” is selected, the volume considers filenames to be different if they’re spelled alike but capitalized differently.

For best performance with volumes that you share using the SMB protocol, leave the option unselected (case insensitive).

When you change case sensitivity, Xsan checks all existing filenames to make sure the change won’t result in filenames being considered the same. This check can take a while.

1. In the Xsan pane of the Server app, select the volume you want to edit.

2. Click the Action pop-up menu , then choose Edit Volume.

3. Select “Use case sensitive file system,” then click OK.

   After you click OK, the volume is unmounted from all SAN computers, then remounted.

You can use the Windows ID Mapping setting for a volume to specify how Windows clients map user and group information to Xsan-compatible user IDs (UIDs) and group IDs (GIDs), which they need to access Xsan volumes.

Windows clients can use these methods to provide UIDs and GIDs:

• Generate IDs from GUID: Windows clients dynamically generate UIDs and GIDs based on globally unique identifier (GUID) information in an Active Directory domain. Choose this method if Mac computers on the SAN are connected (bound) to Active Directory with the default binding options, which automatically generate IDs.

• Use IDs from LDAP (RFC 2307): Windows clients get UID and GID values from the uidNumber and gidNumber attributes in Active Directory records. Choose this method if Mac computers on the SAN are connected to Active Directory with binding options set to map IDs to uidNumber and gidNumber.

1. In the Xsan pane of the Server app, select the volume you want to edit.

2. Click the Action pop-up menu , then choose Edit Volume.

3. Choose a mapping method from the Windows ID Mapping pop-up menu.

   If you choose “Use IDs from LDAP (RFC 2307),” you can change the ID numbers used when a directory record doesn’t include a uidNumber or gidNumber attribute.

4. Click OK.

   Server unmounts the volume from clients and controllers and stops the volume before changing the Windows ID mapping method, then starts the volume and mounts it on each computer on which it was mounted.

Extended attributes are enabled when you create a volume with Xsan 4 or later, unless you deliberately disable them.

When extended attributes are enabled, attributes associated with a file are stored inside the file itself, rather than in separate hidden files. Enabling extended attributes improves file system performance.

• When creating a volume, select "Use native extended attributes,” then click OK.