Verifying that the file systems are clean

Last published : Sep 21, 2026
Verify that all file systems have been cleanly unmounted.
To make sure the file systems are clean
  1. 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.
    1. If a file system is not clean, enter the following commands for that file system:
    \# /opt/VRTS/bin/fsck -V vxfs filesystem
    \# /opt/VRTS/bin/mount -V vxfs filesystem 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 fileset 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.
  1. 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 fileset clone can take several hours.
  2. Repeat step 1 to verify that the unclean file system is now clean.
Related information