Please enter search query.
Search <book_title>...
Storage Foundation 7.4.1 Configuration and Upgrade Guide - Solaris
Last Published:
2019-06-18
Product(s):
InfoScale & Storage Foundation (7.4.1)
Platform: Solaris
- Section I. Introduction and configuration of Storage Foundation
- Section II. Upgrade of Storage Foundation
- Planning to upgrade Storage Foundation
- About the upgrade
- Supported upgrade paths
- Preparing to upgrade SF
- Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches
- Upgrading Storage Foundation
- Performing an automated SF upgrade using response files
- Upgrading SF using Boot Environment upgrade
- Performing post-upgrade tasks
- Optional configuration steps
- Recovering VVR if automatic upgrade fails
- Resetting DAS disk names to include host name in FSS environments
- Upgrading disk layout versions
- Upgrading VxVM disk group versions
- Updating variables
- Setting the default disk group
- Upgrading the Array Support Library
- Converting from QuickLog to Multi-Volume support
- Verifying the Storage Foundation upgrade
- Planning to upgrade Storage Foundation
- Section III. Post configuration tasks
- Section IV. Configuration and Upgrade reference
- Appendix A. Installation scripts
- Appendix B. Configuring the secure shell or the remote shell for communications
- About configuring secure shell or remote shell communication modes before installing products
- Manually configuring passwordless ssh
- Setting up ssh and rsh connection using the installer -comsetup command
- Setting up ssh and rsh connection using the pwdutil.pl utility
- Restarting the ssh session
- Enabling and disabling rsh for Solaris
Verifying that the file systems are clean
Verify that all file systems have been cleanly unmounted.
To make sure the file systems are clean
- Verify that all file systems have been cleanly unmounted:
# echo "8192B.p S" | /opt/VRTS/bin/fsdb filesystem | \ grep clean flags 0 mod 0 clean clean_valueA clean_value value of 0x5a indicates the file system is clean. A value of 0x3c indicates the file system is dirty. A value of 0x69 indicates the file system is dusty. A dusty file system has pending extended operations.
- If a file system is not clean, enter the following commands for that file system:
# /opt/VRTS/bin/fsck -F vxfs filesystem # /opt/VRTS/bin/mount -F vxfs Block_Device mountpoint # /opt/VRTS/bin/umount mountpoint
These commands should complete any extended operations on the file system and unmount the file system cleanly.
A pending large package clone removal extended operation might be in progress if the umount command fails with the following error:
file system device busy
An extended operation is in progress if the following message is generated on the console:
Storage Checkpoint asynchronous operation on file_system file system still in progress.
- If an extended operation is in progress, you must leave the file system mounted for a longer time to allow the operation to complete. Removing a very large package clone can take several hours.
- Repeat step 1 to verify that the unclean file system is now clean.