The section following describes:
VxFS supports files larger than one terabyte. Files larger than 32 terabytes can be created only on 64-bit kernel operating systems and on a VERITAS Volume Manager volume.
Note Applications and utilities such as backup may experience problems if they are not aware of large files. In such a case, create your file system without large file capability.
You can create a file system with large file capability by entering the following command:
# mkfs -V vxfs -o largefiles
-s
size special_device
Specifying largefiles
sets the largefiles
flag, which allows the file system to hold files that are one terabyte or larger in size. The default option is largefiles
. Conversely, the nolargefiles
option clears the flag and prevents large files from being created:
# mkfs -V vxfs -o nolargefiles
-s
size special_device
Note
The largefiles
flag is persistent and stored on disk.
If a mount succeeds and nolargefiles
is specified, the file system cannot contain or create any large files. If a mount succeeds and largefiles
is specified, the file system may contain and create large files.
The mount
command fails if the specified largefiles|nolargefiles
option does not match the on-disk flag.
The mount
command defaults to match the current setting of the on-disk flag if specified without the largefiles
or nolargefiles
option, so it's best not to specify either option. After a file system is mounted, you can use the fsadm
utility to change the large files option.
You can determine the current status of the largefiles flag using the fsadm
:
# fsadm -V vxfs
mount_point | special_device
You can switch capabilities on a mounted file system using the fsadm
command:
# fsadm -V vxfs -o
[no
]largefiles
mount_point
You can also switch capabilities on an unmounted file system:
# fsadm -V vxfs -o
[no
]largefiles
special_device
You cannot change a file system to nolargefiles
if it holds large files.
See the mount_vxfs
(1M), fsadm_vxfs
(1M), and mkfs_vxfs
(1M) manual pages.