Xsan: Volume not visible in Xsan Admin after renaming the volume

When using Xsan Admin to change the name of a volume in OS X Mountain Lion, the renamed volume may no longer appear in Xsan Admin, but will remain available to Xsan clients.

This article has been archived and is no longer updated by Apple.

When the volume was renamed, the format of the volume's configuration file changed from ASCII to XML, and certain settings were removed. Use either of these options to resolve the issue.

Replace your configuration file

  1. Locate the affected configuration file (.cfg) in /Library/Preferences/Xsan/ on the metadata controller.
  2. Replace the file with a backup configuration file for that volume. If you don't have a backup, you can use another configuration file for the same volume from a backup Xsan metadata controller.
  3. Make sure that the name of the replacement file matches the name of the file you replaced.

Use a Perl script

If you don't have a replacement configuration file, you can use a Perl script to modify the current file.

  1. Download and expand this script: cfgconverter.pl.zip.
  2. Open Terminal and use the following command to make the script executable. Substitute the appropriate pathname where indicated.
    sudo chmod +x /pathname/cfgconverter.pl
  3. Use the following command to run the script. Substitute the appropriate pathname and configuration filename where indicated.
    sudo /pathname/cfgconverter.pl /pathname/filename.cfg

The script restores the removed CaseInsensitive, EnforceACLs, and SpotlightSearchLevel settings, then save the file in the appropriate ASCII format.

Learn more

If an Xsan volume is renamed in OS X Mountain Lion v10.8.5, its configuration file format is not changed to XML, and the volume will remain visible in Xsan Admin. However, the CaseInsensitive, EnforceACLs, and SpotlightSearchLevel settings will still be removed. It is recommended you use one of the options listed above to restore these values.

Published Date: