Home > Veritas Storage Foundation™ File System Manual Pages
VXUPGRADE (1M) |
Maintenance Commands |
Only a privileged user can query or upgrade a VxFS file system.
When invoked with the -n option, vxupgrade upgrades the disk layout to the specified version. When invoked without the -n option, vxupgrade prints the disk layout version number of the file system. To perform an upgrade, vxupgrade freezes the file system, allocates and initializes the new structures, frees the space used by the old structures, then thaws the file system.
vxupgrade employs a lock file (lost+found/.fsadm) on the file system to ensure that only one instance of vxupgrade is running at any time. vxupgrade and fsadm cannot run simultaneously, so the lock file also ensures that vxupgrade does not execute while a file system reorganization is in progress. When vxupgrade is invoked for an upgrade, it opens the lock file in the root of the file system specified by mount_point. If the lock file does not exist, it is created. The fcntl(2) system call is used to obtain a write lock on the file. If the write lock fails, vxupgrade fails, assuming that another vxupgrade or fsadm is running.
Upgrading to disk layout Version 6 changes all inodes in the file system. A file system with disk layout Version 5 can be mounted and upgraded to Version 6 disk layout.
You can upgrade a Version 4 disk layout directly to Version 6. The upgrade may fail if there is insufficient free space (see Free Space Requirement below).
Optionally, prior to upgrading a file system to disk layout Version 6, delete all existing Storage Checkpoints. A Storage Checkpoint created on a file system with a disk layout prior to Version 6 stores a complete copy of the inodes at the time it was taken. Thus, a file system with one Storage Checkpoint takes approximately twice as long to upgrade as a file system without Storage Checkpoints. Conversely, a Storage Checkpoint created on a file system with disk layout Version 6 or later stores only the inodes of files whose data blocks were modified. As a result, the time required to upgrade the disk layout Version in the future is less affected by the number of Storage Checkpoints on the file system.
The space and time required to complete the upgrade increases with the number of extended attributes or hard links in the file system. Typical maximum space to convert to a Version 6 disk layout is at least two additional inodes with one block for every inode. The number of inodes is the sum total of inodes across all filesets in the file system (see the fsdb_vxfs(1M) manual page for information on how to obtain the number of inodes in a fileset). Allow at least ten minutes to upgrade for every million inodes in the file system.
Note: Upgrading requires free extents of 8K or greater in size. If a file system has sufficient free space, but no extents greater than or equal to 8K, the upgrade will fail. To ensure that there are 8K extents available, defragment the file system (see the fsadm_vxfs(1M) manual page for information on how to obtain the number of free extents in a file system and how to defragment a file system).
VERITAS File System Administrator's Guide
Last updated: 01 April 2006
Copyright ©2009 Symantec Corporation
All rights reserved.