HP-UX HB v13.00 Ch-06 - Ignite-UX
HP-UX Handbook – Rev 13.00 Page 31 (of 58)
Chapter 06 Ignite-UX
October 29, 2013
Without Online-JFS, a new file system must be created to change the file system to support
largefiles. Check if the file system supports large files with:
# /usr/sbin/fstyp -v /dev/vgxx/lvolx|grep f_flag
f_flag: 16 large files are activated
f_flag: 0 large files are inactive
With Online-JFS
# /usr/sbin/fsadm -F vxfs /file_system_path
If the output shows largefiles, then large files are activated. If it shows nolargefiles large
files are inactive. To change a file system to support large files, do the following:
# /usr/sbin/fsadm -F file_system -o largefiles /dev/vgxx/lvolx
for example
# /usr/sbin/fsadm -F vxfs -o largefiles /dev/vg01/lvol6
In order for clients to be affected by the change if the file system is already exported, run:
# /usr/sbin/exportfs –av
Archive Configuration Policies
When specifying archive content, either via the Ignite-UX GUI or in the make_net_recovery
command line, the following rules apply:
No essential file or directory can be excluded.
Files and directories inside an included directory will be included recursively.
If a symbolic link to a file or directory is included, only the link will be included
in the archive, not the actual file or directory, unless it, too, is included. A
warning will be given when the item itself is a symbolic link.
If a directory is included which contains symbolic links to other files or
directories, the symbolic links will be included but not the referenced files or
directories, unless they, too, are included. No warnings are given regarding these
links.
If a directory contains local mount points, the files and directories under the local
mount points will not be included, by default. This policy can be waived by
specifying the option inc_cross (include directory and cross-mount points), in
the selection interface or command line.