Veritas Storage Foundation Cross-Platform Data Sharing 5.0 AdministratorÆs Guide, HP-UX 11i v3, First Edition, May 2008

50 File system data sharing
Converting the byte order of a file system
should be located in a directory that is not subject to system or local scripts
will remove the file after a system reboot, such as that which occurs with
the /tmp and /var/tmp directories on the Solaris operating system.
The recovery file is almost always a sparse file. The disk utilization of this
file can best be determined by using the following command:
# du -sk filename
The recovery file is used only when the byte order of the file system must be
converted to suit the specified migration target.
6 If you are converting multiple file systems at the same time, which requires
the use of one recovery file per file system, record the names of the recovery
files and their corresponding file systems being converted in the event that
recovery from failures is required at a later time.
7 Based on the information provided regarding the migration target,
fscdsconv constructs and displays the complete migration target and
prompts the use to verify all details of the target. If the migration target
must be changed, enter n to exit
fscdsconv without modifying the file
system. At this point in the process,
fscdsconv has not used the specified
recovery file.
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 either case, 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