Apple Xsan 1.4 - Manual (Page 148)

148 Chapter 7 Solving SAN Problems
Problems Using Command-Line Tools
 If you get the response “command not found” when you try to use an Xsan
command-line tool, add /Library/Filesystems/Xsan/bin/ to your search path or switch
to this folder before you type the command. For example, to use the cvadmin tool:
$ cd /Library/Filesystems/Xsan/bin
$ sudo ./cvversions
 If you get the response “Cannot list FSS - reason -Bad file descriptor” when you run
the cvadmin tool, make sure you are using the tool as the root user. Either log in as
the root user or use the sudo command to run the tool. For example:
$ sudo cvadmin
 If you get the response “No manual entry for...” when you try to view the man
page for an Xsan command-line tool, you need to add the Xsan man pages folder
/Library/Filesystems/Xsan/man to your man search path. One way to do this is to add
the following line to the file /usr/share/misc/man.conf (Mac OS X or Mac OS X v10.4.)
or the file /etc/manpath.config (Mac OS X or Mac OS X v10.3.):
MANPATH /Library/Filesystems/Xsan/man
A LUN Doesn’t Have as Much Space as Expected
To make striping across LUNs possible, Xsan automatically adjusts LUN sizes to make all
LUNs in a storage pool the same size as the smallest LUN in the pool. Xsan doesn’t use
the extra space on larger LUNs when you mix LUNs of different sizes in the same
storage pool.