< Previous  | TOC | Index | Next  >

Make sure the file systems are clean

Prior to upgrading to release 5.0, verify that all file systems have been cleanly unmounted by running the fsdb command from the existing release of File System.

1. Verify that all file systems have been cleanly unmounted:

   # echo "8192B.p S" | fsdb -F vxfs <Raw_Device> | grep clean

flags 0 mod 0 clean clean_value

A clean_value value of 0x5a indicates the file system is clean, 0x3c incidates the file system is dirty, and 0x69 indicates the file system is dusty. A dusty file system has pending extended operations.

2. If a file system is not clean, enter the following commands for that file system:

   # fsck -F vxfs filesystem

   # mount -F vxfs [Block_Device] [mountpoint]

   # umount [mountpoint]

   This should complete any extended operations that were outstanding on the file system and unmount the file system cleanly.

   There may be a pending large fileset clone removal extended operation if the umount command fails with the following error:

file system device busy

You know for certain that an extended operation is pending if the following message is generated on the console:

Storage Checkpoint asynchronous operation on file_system

file system still in progress.

3. If an extended operation is pending, 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.
4. Repeat step 1 to verify that the unclean file system is now clean.