Please enter search query.
Search <book_title>...
Storage Foundation 7.2 Configuration and Upgrade Guide - Solaris
Last Published:
2018-03-06
Product(s):
InfoScale & Storage Foundation (7.2)
Platform: Solaris
- Section I. Introduction and configuration of Storage Foundation
- Section II. Upgrade of Storage Foundation
- Planning to upgrade Storage Foundation
- Preparing to upgrade SF
- Upgrading Storage Foundation
- Performing an automated SF upgrade using response files
- Upgrading SF using Boot Environment upgrade
- Performing post-upgrade tasks
- Upgrading the Array Support Library
- 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
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_value
A 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.