File systems must be cleanly unmounted before upgrading to VERITAS File System 4.0 or 4.1 from any previous version.

Article:TECH30311  |  Created: 2006-01-16  |  Updated: 2006-01-16  |  Article URL http://www.symantec.com/docs/TECH30311
Article Type
Technical Solution

Product(s)

Environment

Issue



File systems must be cleanly unmounted before upgrading to VERITAS File System 4.0 or 4.1 from any previous version.

Error



log replay in progress
UX:vxfs fsck: ERROR: V-3-20749: file system does not contain a valid log
UX:vxfs fsck: ERROR: V-3-20750: cannot perform log replay

Solution



Due to enhancements to the log structure in VERITAS File System 4.0 and 4.1, the fsck utility from these releases is unable to replay file system intent logs created by previous versions. For this reason, all file systems must be cleanly unmounted before the upgrade to File System 4.0 or 4.1.

WARNING:  Failure to follow this recommended procedure could result in prolonged outages and possible loss of recent file system updates. File systems that were not clean at the time of the upgrade will require a full fsck and could experience long delays during both the fsck and mount processes.  Recent updates to the file system could be lost as no log replay would take place.


Prevention procedure prior to upgrading to VERITAS File System 4.0 or 4.1:

Prior to uninstalling the current release and upgrading to release 4.0 or 4.1, verify that all file systems have been cleanly unmounted by running the fsdb command from the existing release of File System.

For Solaris and HP-UX:
# echo "8192B.p S" | fsdb -F vxfs <Raw_Device> | grep clean

For Linux:
# echo "8192B.p S" | fsdb -t vxfs <Raw_Device> | grep clean

For AIX:
# echo "8192B.p S" | /opt/VRTSvxfs/sbin/fsdb <Raw_Device> | grep clean

Output resembles the following:

flags 0 mod 0 clean 3c

Values for the clean flag are:

0x5a Indicates the file system is clean
0x3c Indicates the file system is dirty
0x69 Indicates the file system is dusty (has pending extended operations).

For a file system that is not clean, perform the following commands to unmount the file system cleanly.

For Solaris and HP-UX:
# fsck -F vxfs [Raw_Device]
# mount -F vxfs [Block_Device] [mountpoint]
# umount [mountpoint]

For Linux:
# fsck -t vxfs [Raw_Device]
# mount -t vxfs [Block_Device] [mountpoint]
# umount [mountpoint]

For AIX:
# fsck -V vxfs [Raw_Device]
# mount -V vxfs [Block_Device] [mountpoint]
# umount [mountpoint]

This should complete any extended operations that were outstanding on the file system. Run the fsdb command again to verify that the file system is clean

If the umount failed with the "file system device busy" error, there may be a pending large fileset clone removal extended operation. If the "Storage Checkpoint asynchronous operation on <file_system> file system still in progress" message is generated on the console, an extended operation is pending.

In this special case, you must leave the file system mounted for a longer time to allow the clone removal extended operation to complete. Removing a very large fileset clone can take several hours.

Once fsdb reports that all file systems are clean, proceed with the upgrade


Recovery procedure post VERITAS File System 4.0 or 4.1 upgrade:

If the 4.0 or 4.1 release has been installed and fsck is reporting the following error:

log replay in progress
UX:vxfs fsck: ERROR: V-3-20749: file system does not contain a valid log
UX:vxfs fsck: ERROR: V-3-20750: cannot perform log replay

do not perform a full fsck on the file system. Do not upgrade the file system disk layout version (with vxfsconvert or vxupgrade). To clean the file systems safely, downgrade to the previously installed VERITAS File System version, and run the prevention procedure above.

Do not downgrade to a previous version if a file system disk layout upgrade has already been performed. If the disk layout upgrade has already been completed, contact Symantec Enterprise Technical Support for assistance





Legacy ID



265504


Article URL http://www.symantec.com/docs/TECH30311


Terms of use for this information are found in Legal Notices