Enter your product and environment information to create a Risk Assessment checklist.
Product family:
Product:
Platform:
Product version:


 

  

Custom Reports Using Data Collectors

Full fsck required

Check category: Availability


Check description: Check whether the File System(VxFS)s mounted on a system are marked for a full file system check (fsck)


Check procedure:

  • Checks whether the File System(VxFS) package is installed on the system.
  • Identifies all available File Systems(VxFS) on the system, and determines whether the full fsck flag is set for each one.


Check recommendation: Repairing file systems that require a full fsck is a time-consuming operation; the time required is proportional to the size of the file system. These files systems will require a full fsck before they can be mounted again; plan any downtime accordingly.


Learn More...

fsck: manual page

Sufficient memory for full fsck

Check category: Availability


Check description: Checks whether enough memory is available on the system for a full file system check (fsck) to run on a mounted File System(VxFS).


Check procedure:

  • Identfies any mounted File System(VxFS)s on the system.
  • For each of the file systems, determines the number of file system blocks, inodes and allocation units.
  • Collects system information such as the available physical and swap memory.
  • Calculates the memory required to perform a full fsck on each file system.
  • Determines whether the required memory is available on the system.


Check recommendation: You do not have enough physical and virtual memory to run a full file system check (fsck) of this file system. In most situations, VxFS replays the intent log, avoiding the need for a full fsck. In rare circumstances, however, a full fsck is required. If you are not at or above Storage Foundation version 5.0 MP3, consider upgrading. 5.0MP3 and higher have reduced memory requirements for a full fsck. Alternately, you can add physical or virtual memory. Physical memory is preferred because using swap space increases the time to complete the check.


Learn More...

fsck: manual page

Removable VxFS File System checkpoints

Check category: Availability


Check description: Checks whether all the Storage Checkpoints of the mounted VxFS File Systems are removable.


Check procedure:

  • Identifies the mounted VxFS File Systems on the system.
  • Checks whether the Storage Checkpoints of each of the mount points were created with the removable attribute.


Check recommendation: The Storage Checkpoints are not removable. In most configurations, Storage Checkpoints should be removable to reduce the chance of an ENOSPC error on the primary data. To create a removable Storage Checkpoint, enter :
#fsckptadm -r create <checkpoint> <mountpoint>


Learn More...

Removable Storage Checkpoints
Creating a Storage Checkpoint
Space management considerations

File System disk layout version

Check category: Availability


Check description: Checks whether the File System disk layout version is supported with the installed Storage Foundation / InfoScale version, and whether the file system size is close to the maximum supported by the disk layout version and block size.


Check procedure:

  • Determines the Storage Foundation / InfoScale version installed on the system.
  • Determines the size of the file systems mounted on the system.
  • Checks whether the file system disk layout version is compatible with the Storage Foundation / InfoScale version installed on the system.
  • Checks whether the file system size is close to the maximum supported by the disk layout version and block size.


Check recommendation: The recommendations are summarized in the following two cases:

i) Case 1 : Ensure that disk layout version of any VxFS File Systems mounted on the system are supported by the installed Storage Foundation / InfoScale software. Once you upgrade a disk layout, you cannot downgrade it. Refer to the upgrade recommendations below.

ii) Case 2 : Ensure that the VxFS File Systems mounted on the system are not approaching the maximum size allowed by that disk layout version and block size. It is recommended upgrading the file system disk layout version. Refer to the following table to view the maximum file system size supported by various file system disk layout versions:

FS block size (in K)Maximum FS size supported (in TB) for FS disk layout Version 5Maximum FS size supported (in TB) for FS disk layout Version 6 and higher
1432
2864
416128
832256

 It is recommended upgrading the file system disk layout version in the following cases:

i) When the system has any Storage Checkpoints. On older version file systems, Storage Checkpoints take a long time to create and can make fsck run longer in the event of a crash.

ii) When the system does not have too many inodes. In an upgrade to a higher file system disk layout version, every inode is modified.

iii) When the system is running Storage Foundation Cluster File System, it is recommended that you upgrade the file system disk layout version to Version 7 or higher, which provides significant performance gains.


Learn More...

About disk layouts

VxFS File System resize anomaly

Check category: Availability


Check description: When the size of a VxFS File System is either a multiple of or just under a multiple of 32 K file system blocks, you cannot grow the file system when it is 100% full. This check identifies the file systems that meet this size criteria.


Check procedure:

  • Identifies the VxFS File Systems present on the system.
  • Obtains the size of all the VxFS File Systems present on the system.
  • Verifies whether the file system size is a multiple of or just under a multiple of 32 K blocks.


Check recommendation: The size of the VxFS File System(s) is either a multiple of 32k file system blocks or it is just under a multiple of 32K file system blocks. In this scenario, the file system cannot be grown when it is 100% full. It is recommended that you address the issue in one of the following ways:

i) Upgrade to the 5.1 or higher version of your product (for example, Storage Foundation 5.1). This issue does not exist in 5.1 and higher version.

ii) Resize the file system so that it is either:

a) Larger than the multiple of 32 K file system blocks. For example, if your file system is 32768 KB in size, it contains 1 32 K block. Resize the file system to x KB where, 32768 < x < 65536.

b) Less than the multiple of 32 K blocks minus 68 K file system blocks. For example, if your file system is 32768 KB in size, it contains 1 32 K block. Resize the file system to less than 32768 - 68 = 32700 KB

iii) Create a 64 K placeholder file in the lost+found directory on the mounted file system. When the file system is 100% full, delete the placeholder file and extend the file system. Use the following command to create the placeholder file:

dd if=/dev/zero of=DELETE_ONLY_WHEN_FS_FULL_TO_AVOID_FS_RESIZING_PROBLEM bs=64K count=1

One can resize the volume using : # vxresize -g <diskgroup> <volume> <new_length>


Learn More...

Enhancement to resize and grow a VxFS file system.
Resizing a file system
Extending a file system using fsadm

Unmounted VxFS File System(s)

Check category: Availability


Check description: Checks for unmounted VxFS File System(s) that have entries in filesystem table and valid underlying devices. Note: Following platform specific filesystem table are referred in the check: Linux: /etc/fstab AIX: /etc/filesystems HP-UX: /etc/fstab Solaris: /etc/vfstab


Check procedure:

  • Reads the VxFS File System entries in the fstab file.
  • Checks whether these file systems are mounted.
  • For any file system that is not mounted, checks whether an underlying volume exists.


Check recommendation: It is recommended that removing any stale entries and deleting the corresponding underlying volumes to reclaim space.


Learn More...

Editing the filesystems file
Unmounting the file system
Removing a volume

Package Consistency

Check category: Availability


Check description: Checks that packages installed across all the nodes in a cluster are consistent


Check procedure:

  • Identifies the packages installed on all the nodess in a cluster.
  • Verifies that the package installed and its version are consistent across all the nodes in the cluster.


Check recommendation: Ensure that packages installed on all the nodes in a cluster are consistent and package versions are identical. Inconsistent packages can cause errors in application fail-over.



Quick I/O (QIO) in a cluster

Check category: Availability


Check description: Checks the quick I/O (QIO) license across all nodes in a single cluster to ensure that each node has the same QIO license feature.


Check procedure:

  • Checks whether VxVM Volume Manager, Cluster Server (VCS), and Cluster File System (CFS) packages are installed on the system.
  • Verifies whether the QIO/ODM license feature is consistent across all nodes in the cluster.


Check recommendation: The QIO/ODM license feature should be consistent across all nodes in the cluster.


Learn More...

Mount failures
Mount failures in SFCFS

VCS replication agent

Check category: Availability


Check description: Checks for the presence of VCS replication agents on the system.


Check procedure:

  • Identifies the VCS replication agents that are configured and installed.
  • Verifies whether the VCS replication agents have correct versions.


Check recommendation: It is recommended that you install the missing VCS replication agents listed in the output details.



Fragmented VxFS File System

Check category: Best practices


Check description: Checks VxFS File System fragmentation. If a file system is too fragmented, the check recommends defragmentation.


Check procedure:

  • Identifies the mounted VxFS File Systems on the system.
  • Checks whether the file systems are fragmented.


Check recommendation: You should defragment the file systems to improve performance and reduce recovery time.

Defragmentation creates I/O and uses CPU, so you should schedule defragmentation during periods of low system activity. A conservative approach is to defragment one file system at a time, that is, to wait for one defragmentation to complete before starting the next. Defragmentation time varies depending on factors including the file system size and the number of files. Defragmentation can run for extended periods.


Learn More...

Monitoring fragmentation

Verify software patch level

Check category: Best practices


Check description: Checks whether the installed Storage Foundation / InfoScale products are at the latest software patch level.


Check procedure:

  • Identifies all the Storage Foundation / InfoScale products installed on the system.
  • Verifies whether the installed products have the latest software versions that are available for download.


Check recommendation: To avoid known risks or issues, it is recommended that you install the latest versions of the Storage Foundation / InfoScale products on the system.



VxFS File System intent log size

Check category: Performance


Check description: If the disk layout is version 6 or later, this check compares the size of the VxFS File System and the size of the intent log. If the intent log is too small compared to the VxFS file system, the report recommends resizing the intent log to meet the standards. File System (VxFS) uses an intent log to improve recoverability while maintaining performance. When VxFS creates a file system, it chooses the intent log size. The larger the VxFS file system, the larger the intent log. If you resize the VxFS file system, the intent log size does not change, This can result in a log size smaller than the recommended default. Metadata-intensive workloads can benefit from a larger intent log. This is because if a high number of transactions come in a short period of time, the log fills and must be flushed before accepting new transactions. Metadata-intensive workloads usually add, delete, append to, or truncate files; change file names, permissions, directories, access control lists (ACLs), or owners; or use Storage Checkpoints. Database workloads which pre-allocate large files and only read and write to those files are not usually metadata-intensive -- unless you use Storage Checkpoints. Therefore, they are less likely to see performance benefits from a larger log. You can resize a VxFS file system when it is mounted, online, and actively receiving application I/O with the vxresize command.


Check procedure:

  • For each mounted VxFS File System with disk layout version 6 or greater, determines both the intent log size and the VxFS file system size.
  • Compares the actual intent log size with the recommended intent log size.


Check recommendation: The VxFS file system(s) have undersized intent logs, which can impact performance. It is recommended to increase your intent log size to meet the standards.


Learn More...

Intent log size
fsadm_vxfs: manual page
mkfs_vxfs: manual page

SmartIO feature awareness

Check category: Performance


Check description: Checks whether Solid State Drives (SSDs) or flash drives are attached to the server. It also recommends the right version of Storage Foundation and High Availability / InfoScale software that have the SmartIO feature to bring better performance, reduced storage cost and better storage utilization.


Check procedure:

  • Checks whether VxVM is installed.
  • Checks the version of installed VxVM.
  • Verifies whether the platform is other than HP-UX.
  • Checks whether SSDs or Flash drives are attached to the system.
  • Verifies whether the SmartIO feature is in use.


Check recommendation: The recommendation is summarized in below cases:

Case 1 : SSDs or flash drives are detected on the Linux system with the Storage Foundation software version earlier than 6.1 installed. It is recommended to upgrade the Storage Foundation software to 6.1 or higher version which enables you to use the SmartIO feature, which improves performance, reduces storage costs and brings better storage utilization for the applications running on the servers.

Case 2 : SSDs or flash drives are detected on the AIX/Solaris system with the Storage Foundation software version earlier than 6.2 installed. It is recommended to upgrade the Storage Foundation software to 6.2 or higher version which enables you to use the SmartIO feature, which improves performance, reduces storage costs, and brings better storage utilization for the applications running on the servers.

Case 3 : SSDs or flash drives are detected on the Linux system with Storage Foundation software version 6.1 installed, but SmartIO feature is not detected. It is recommended that you use the SmartIO feature which improves performance, reduces storage costs, and brings better storage utilization for the applications running on the servers. Please refer the documentation link(s).

Case 4 : SSD or flash drives are detected on the system with Storage Foundation software version 6.2 or higher installed, but SmartIO feature is not detected. It is recommended that you use the SmartIO feature which improves performance, reduces storage costs, and brings better storage utilization for the applications running on the servers. Please refer the documentation link(s).

Case 5 : Storage Foundation software version 6.2 or higher is found on the AIX/Linux/Solaris system without any SSD or flash drives. SSDs or flash drives are more efficient since they provide faster data access and have a smaller footprint than traditional spinning disks. The data center uses solid-state technologies in many form factors: in-server, all flash arrays, all flash appliances, and mixed with traditional HDD arrays. Each form factor offers a different value proposition. SSDs also have many connectivity types: PCIe, FC, SATA, and SAS. It is recommended that you use the SmartIO feature that offers data efficiency on your SSDs through I/O caching, which improves performance, reduces storage costs, and brings better storage utilization for the applications running on the servers.

Case 6 : Storage Foundation software version 6.1 is found on the Linux system without any SSDs or flash drives. SSDs or flash drives are more efficient since they provide faster data access and have a smaller footprint than traditional spinning disks. The data center uses solid-state technologies in many form factors: in-server, all flash arrays, all flash appliances, and mixed with traditional HDD arrays. Each form factor offers a different value proposition. SSDs also have many connectivity types: PCIe, FC, SATA, and SAS. It is recommended that you use the SmartIO feature that offers data efficiency on your SSDs through I/O caching, which improves performance, reduces storage costs, and brings better storage utilization for the applications running on the servers.

Case 7 : Storage Foundation software version 6.1 is found on the AIX/Solaris system without any SSDs or flash drives. It is recommended to upgrade the Storage Foundation software to 6.2 or higher version and use the SmartIO feature that offers data efficiency on your SSDs through I/O caching which improves performance, reduces storage costs, and brings better storage utilization for the applications running on the servers. SSDs or flash drives are more efficient since they provide faster data access and have a smaller footprint than traditional spinning disks. The data center uses solid-state technologies in many form factors: in-server, all flash arrays, all flash appliances, and mixed with traditional HDD arrays. Each form factor offers a different value proposition. SSDs also have many connectivity types: PCIe, FC, SATA, and SAS.



File System old Storage Checkpoint

Check category: Utilization


Check description: Checks for VxFS File System Storage Checkpoints that are older than !param!HC_CHK_FS_OLD_CHECKPOINT_DAYS_OLD!/param!, which is set in the sortdc.conf file.


Check procedure:

  • Identifies all the VxFS File System mount points present on the system.
  • Identifies all the mounted Storage Checkpoints in the mount points, and checks whether they are older than the threshold value.


Check recommendation: It is recommended that you delete any old VxFS File System Storage Checkpoints that you no longer require in order to reclaim file system space.


Learn More...

How to remove a Storage Checkpoint

VxFS File System utilization

Check category: Utilization


Check description: Checks VxFS File System utilization. It lists out the VxFS File Systems whose percentage of usage space is less or more than the percentage specified in the user-defined parameter !param!HC_CHK_FS_USAGE_PERCENT_MIN!/param! and !param!HC_CHK_FS_USAGE_PERCENT_MAX!/param! respectively. These two parameters are set in sortdc.conf file.


Check procedure:

  • Identifies the used space for all the VxFS file systems on the system.
  • Checks whether the percentage of used space is greater than the threshold value.


Check recommendation: The VxFS file system(s) listed in output are either under-utilized or over-utilized. It is recommended that you shrink the under-utilized VxFS file system and its volume, and use the freed space elsewhere. It is better to defragment the over-utilized VxFS file systems and to add extra storage.


Learn More...

Shrinking a file system
Extending a file system using fsadm

VxFS volume and file system size

Check category: Utilization


Check description: Checks if any of the VxFS file system and underlying VxFS volume size is different and the size difference is greater than the size specified in the user-defined parameter !param!HC_CHK_FS_VOLS_SIZE_DIFF_THRESHOLD!/param!, which is set in the sortdc.conf file.


Check procedure:

  • Identifies the mounted VxFS file systems and determines their size.
  • Identifies the volumes or volume set used to mount each of the file systems and determines its size.
  • Compares the size of the file system with the size of the underlying volume or volume set. Checks whether the size difference is greater than the user-defined parameter HC_CHK_FS_VOLS_SIZE_DIFF_THRESHOLD, which is set in the sortdc.conf file.


Check recommendation: To make the best use of volume space, the file system should be the same size as the volume or volume set.
The failure can be summarized in one of the following cases:

Case I: The file system size is less than underlying volume by a threshold parameter of HC_CHK_FS_VOLS_SIZE_DIFF_THRESHOLD.
You should either grow the file system using the fsadm command or shrink the volume using the vxassist command.

Case II: The file system is larger than underlying volume. This can happen due to execution of incorrect command (vxassist) for shrinking the volume after file system creation.

Run the following commands.
To grow the file system:
# fsadm [-F vxfs] [-b <newsize>] [-r rawdev] mount_point
To shrink :
#vxassist -g <mydg> shrinkby <vol> <len>
or
#vxassist -g <mydg> shrinkto <vol> <newlen>


Learn More...

fsadm_vxfs: manual page
vxassist: manual page
vxresize: manual page

 
Read and accept Terms of Service