Home > Veritas Storage Foundation™ File System Manual Pages
After starting a conversion and before actually modifying the file system, you will be prompted to confirm the operation. If you choose not to proceed with the operation, the file system will be left unchanged.
The process of converting a file system's byte order can fail for various reasons: system failure, power failure, command failures, user interruption, etc. A temporary file is created by fscdsconv as specified by the -f option so that the file system can be restored to its original condition in the event of a failure. In case of a failure, fscdsconv must be reinvoked with the -r option.
The file system that contains the recovery file must not be a temporary file system that might be cleaned up after a system reboot or whose data integrity is less than the data integrity of the file system being converted. For example, if the file system being converted is on a mirrored volume, then the recovery file should also be on a file system that is capable of tolerating device failures.
The recovery file is not removed when the conversion completes.
See the VERITAS Storage Foundation Cross-Platform Data Sharing Administrator's Guide for more information.
If quotas will be used on the file system, before unmounting it, remove the quotas and quotas.grp files. Unmount the file system, then use fscdsconv to convert the file system. On the system to which the file system is being migrated, mount the file system with quotas turned off. Edit the quotas and quotas.grp files to input the usage limits. Turn on quotas for the file system.
fscdsconv -f /fs2/recovery1 \ /dev/vx/rdsk/dg1/fs1
The following command recovers the file system /dev/vx/rdsk/dg1/fs1 after a failure, using the recovery file recovery1 located on the file system fs2:
fscdsconv -r -f /fs2/recovery1 \ /dev/vx/rdsk/dg1/fs1
VERITAS Storage Foundation Cross-Platform Data Sharing Administrator's Guide
Last updated: 01 April 2006
Copyright ©2009 Symantec Corporation
All rights reserved.