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

49File system data sharing
Converting the byte order of a file system
To convert the byte order of a file system
1 Determine the disk layout version of the file system that you will migrate:
# fstyp -v /dev/vx/dsk/filesystem | grep version
magic a501fcf5 version 7 ctime Thu Jun 1 16:16:53 2006
Only file systems with Version 6 or later disk layout can be converted. If the
file system has an earlier disk layout version, convert the file system to
Version 6 or Version 7 disk layout before proceeding.
See the
vxfsconvert(1M) manual page.
See the
vxupgrade(1M) manual page.
2 Perform a full file system back up. Failure to do so could result in data loss or
data corruption under some failure scenarios in which restoring from the
backup is required.
3 Designate a file system with free space where
fscdsconv may create a file
that will contain recovery information for usage in the event of a failed
conversion.
Depending on the nature of the file system to be converted, for example if it
is mirrored, you may wish to designate the recovery file to reside in a file
system with the same level of failure tolerance. Having the same level of
failure tolerance reduces the number of failure scenarios that would require
trestoration from the backup.
4 Unmount the file system to be converted:
# umount mount_point
5 Use the fscdsconv command to export the file system to the required target:
# fscdsconv -f recovery_file -t target -e special_device
target specifies the system to which you are migrating the file system.
See “Specifying the migration target” on page 42.
recovery_file is the name of the recovery file to be created by the
fscdsconv command. special_device is the raw device or volume that
contains the file system to be converted.
Include the file system that you chose in step 3 when designating the
recovery file.
For example, if the file system chosen to contain the recovery file is
mounted on /data/fs3, the recovery file could be specified as
/data/fs3/jan04recovery. If there is not enough disk space on the
chosen file system for the recovery file to be created, the conversion aborts
and the file system to be converted is left intact.
The recovery file is not only used for recovery purposes after a failure, but
is also used to perform the conversion. The directory that will contain the
recovery file should not allow non-system administrator users to remove or
replace the file, as this could lead to data loss or security breaches. The file