Change Xsan volume settings in macOS Server
If your SAN volume has special configuration requirements, you can change the standard volume settings when you create a volume.
You can also change these settings for an existing volume, but you can’t disable the extended attributes option. (Once enabled, extended attributes can’t be disabled.)
Note: To disable extended attributes, you must destroy and re-create the volume.
Enable access control lists
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.
Note: If you enable ACLs but your SAN includes clients that don’t support them, don’t use those clients to change file or folder ownership information, or inconsistencies might result.
In the Server app
sidebar, select Xsan from the list of advanced services.Select the volume you want to edit.
Click
and choose Edit Volume.Select “Use access control lists,” then click OK.
After you click OK, the volume is unmounted from all SAN computers, then remounted.
Enable case sensitivity
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.
In the Server app
sidebar, select Xsan from the list of advanced services.Select the volume you want to edit.
Click
and choose Edit Volume.Select “Use case sensitive file system,” then click OK.
After you click OK, the volume is unmounted from all SAN computers, then remounted.
Map Windows user and group IDs
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.
Important: To avoid ID conflicts, be sure all computers on the SAN use the same Active Directory domain and the same method of ID mapping.
In the Server app
sidebar, select Xsan from the list of advanced services.Select the volume you want to edit.
Click
and choose Edit Volume.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.
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.
Enable native extended attributes
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.
Important: You can enable extended attributes only when you create a volume. Additionally, you can’t disable extended attributes. Enabling them on a volume is a one-way process that 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.
When creating a volume, select "Use native extended attributes,” then click OK.
Mount the volume ignoring ownership
When you enable the Ignore Ownership option, the volume is mounted with the noowners flag, as documented in the mount(8) man page.
In the Server app
sidebar, select Xsan from the list of advanced services.Select the volume you want to edit.
Click
and choose Edit Volume.Select Ignore Ownership, then click OK.