HP-UX Reference (11i v1 00/12) - 1M System Administration Commands N-Z (vol 4)

__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man1m/naaagt.1m
________________________________________________________________
___ ___
v
vxfsconvert(1M) vxfsconvert(1M)
unknown inode type is detected during the conversion, vxfsconvert ignores it.
Conversion Process
To prepare a file system for conversion:
• Unmount the filesystem and make sure it is clean (you may need to use fsck(1M) to clean the
filesystem). vxfsconvert cannot convert a mounted or dirty file system.
• Do a full backup on the file system before starting the conversion process.
Now run vxfsconvert . vxfsconvert does the following steps to convert a file system:
1. Examines the superblock to make sure it is marked CLEAN.
2. Based on information in the file system superblock, sets up VxFS metadata. This includes initializ-
ing all metadata required by the VxFS Version 4 disk layout (for example OLT, log, structural
fileset). At this time, the original file system superblock is marked DIRTY unless you specified the
-e or -s option.
3. Reads every inode in the file system and converts it to a VxFS inode.
4. For every regular file inode,
vxfsconvert allocates and initializes enough extent data to map
all of the file’s data blocks. This translates only the representation of the file’s data blocks from the
old format to that of VxFS. It never copies or relocates user data blocks.
5. For every directory inode,
vxfsconvert allocates sufficient disk space to hold all the directory
entries. For every directory entry in that directory, vxfsconvert converts it to a VxFS direc-
tory entry and writes all converted directory blocks.
6. Converts all symbolic link, character special, block special, fifo, and socket inodes to VxFS.
7. Converts HFS ACL entries to the respective VxFS ACL entries. Only the entries that comply with
the VxFS ACL standard are converted. The compliant entries are those that specify permissions
for either a user or a group, but not both. That is, entries of format (user.%)
and (%.group)
will be converted, while entries of format (user.group) will be omitted. For files with both sup-
ported and unsupported entries all supported entries will be converted, but unsupported entries
will be omitted.
Up to this point, all metadata of the original file system is intact and the conversion process can be stopped.
The file system can be used after you run the original file system-specific fsck
. If you specified the -e or
-s option, running the file system-specific fsck is not required.
8. If all above steps completed successfully vxfsconvert asks whether to commit the conversion.
It waits for the user response unless the -y or -n option was specified.
9. vxfsconvert replaces the original superblock with the VxFS superblock and clears any alter-
nate superblocks written by the original file system. The VxFS superblock is never written if you
have specified the -n or -e option. After the superblock is overwritten, the original file system is
no longer accessible; it is now a VxFS file system.
Now you must run the VxFS-specific full fsck on the converted file system. During pass 4, fsck
displays several error messages that require a yes response to complete the conversion process. These
errors occur because vxfsconvert does not create all metadata files; you must run fsck to complete
the process. No error messages display during passes zero through three. The following is sample
fsck
output after successful conversion.
# fsck -F vxfs -y -o full /dev/vg01/rlvol5
superblock indicates that intent logging was disabled
cannot perform log replay
pass0 - checking structural files
pass1 - checking inode sanity and blocks
pass2 - checking directory linkage
pass3 - checking reference counts
pass4 - checking resource maps
fileset 1 au 0 imap incorrect - fix (ynq)y
fileset 1 au 0 iemap incorrect - fix (ynq)y
fileset 999 au 0 imap incorrect - fix (ynq)y
fileset 999 au 0 iemap incorrect - fix (ynq)y
corrupted CUT entries, clear? (ynq)y
HP-UX Release 11i: December 2000 − 2 − Section 1M−−1049
___
___