Veritas Storage Foundation 5.1 SP1 Advanced Features Administrator"s Guide (5900-1503, April 2011)

8
If the byte order of the file system must be converted to migrate the file
system to the specified target, fscdsconv prompts you to confirm the
migration. Enter y to convert the byte order of the file system. If the byte
order does not need to be converted, a message displays indicating this fact.
9
The fscdsconv command indicates if any files are violating the maximum
file size, maximum UID, or maximum GID limits on the specified target and
prompts you if it should continue. If you must take corrective action to ensure
that no files violate the limits on the migration target, enter n to exit
fscdsconv. At this point in the process, fscdsconv has not used the specified
recovery file.
If the migration converted the byte order of the file system, fscdsconv created
a recovery file. The recovery file is not removed after the migration completes,
and can be used to restore the file system to its original state if required at a
later time.
10
If a failure occurs during the conversion, the failure could be one of the
following cases:
■ System failure.
■ fscdsconv failure due to program defect or abnormal termination resulting
from user actions.
In such cases, the file system being converted is no longer in a state in which
it can be mounted or accessed by normal means through other VxFS utilities.
To recover the file system, invoke the fscdsconv command with the recovery
flag, -r:
# fscdsconv -r -f recovery_file special_device
When the -r flag is specified, fscdsconv expects the recovery file to exist
and that the file system being converted is the same file system specified in
this second invocation of fscdsconv.
11
After invoking fscdsconv with the -r flag, the conversion process will restart
and complete, given no subsequent failures.
In the event of another failure, repeat 10.
Under some circumstances, you will be required to restore the file system
from the backup, such as if the disk fails that contains the recovery file.
Failure to have created a backup would then result in total data loss in the
file system. I/O errors on the device that holds the file system would also
require a backup to be restored after the physical device problems are
addressed. There may be other causes of failure that would require the use
of the backup.
Migrating data between platforms
File system considerations
496