The following are the best practices for creating file systems:

• Ensure all the disks (LUNs) in each storage pool have an identical hardware configuration.

  Best performance results from a striped file system that spans similar disks. The more closely you match the disks by speed, capacity, and interface type, the better the performance you can expect. When striping across several disks of varying speeds, performance is no faster than that of the slowest disk.

• Create striped file systems rather than simple file systems when creating your file systems.

  See About striping file systems.

• In a given storage pool, create all the file systems with the same number of columns.

• Ensure that the number of disks in each storage pool is an exact multiple of the number of columns used by the file systems created in that storage pool.

• Consider how many disks you need to add to your storage pool to grow your striped file systems.

  A 5-TB file system using five columns cannot be grown in a storage pool containing 8*1-TB disks, despite having 3 TB of disk space available. Instead create the file system with either four or eight columns, or else add 2*1-TB disks to the pool. See further examples in the table.

  Use case	Action	Result
  storage pool with eight disks of the same size (1 TB each)	Create a 5 TB striped file system with five columns.	You cannot grow the file system greater than 5 TB, even though there are three unused disks.
  storage pool with eight disks of the same size (1 TB each)	Create a 5 TB striped file system with eight columns.	You can grow the file system to 8 TB.
  storage pool with eight disks of the same size (1 TB each)	Create a 4 TB striped file system with four columns.	You can grow the file system to 8 TB.
  storage pool with eight disks of the same size (1 TB each)	Create a 3 TB striped file system with three columns.	You cannot grow the file system to 8 TB.
  storage pool with eight disks of the different sizes (3 are 500 GB each, and 5 are 2 TB each)	Create an 8 TB striped file system with eight columns.	You cannot create this 8-TB file system.

• Consider the I/O bandwidth requirement when determining how many columns you require in your striped file system.

  Based on the disks you have chosen, I/O throughput is limited and potentially restricted. Figure: LUN throughput - details on the LUN throughput restrictions describes the LUN throughput restrictions.

• Consider populating each storage pool with the same number of disks from each HBA. Alternatively, consider how much of the total I/O bandwidth that the disks in the storage pool can use.

  If you have more than one card or bus to which you can connect disks, distribute the disks as evenly as possible among them. That is, each card or bus must have the same number of disks attached to it. You can achieve the best I/O performance when you use more than one card or bus and interleave the stripes across them.

• Use a stripe unit size larger than 64 KB. Performance tests show 512 KB as the optimal size for sequential I/O, which is the default value for the stripe unit. A greater stripe unit is unlikely to provide any additional benefit.

• Do not change the operating system default maximum I/O size of 512 KB.

• Veritas recommends that you do not create a file system whose name format is such as <file system name_integer>. This is because such file names are reserved for internal objects and may lead to file system creation errors.