unixdev.net


Switch to SpeakEasy.net DSL

The Modular Manual Browser

Home Page
Manual: (HP-UX-11.11)
Page:
Section:
Apropos / Subsearch:
optional field



 vxupgrade(1M)						       vxupgrade(1M)




 NAME
      vxupgrade - upgrade the disk layout of a VxFS file system

 SYNOPSIS
      /usr/sbin/vxupgrade [-n new_version] [-r rawdev] mount_point

 DESCRIPTION
      vxupgrade prints the current disk layout version number for a VxFS
      file system or upgrades the file system to a new disk layout.
      vxupgrade operates on file systems mounted for read/write access:
      mount_point must be a mounted VxFS file system.  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, and then thaws the file system.  This process should not
      keep the file system frozen for more than a few seconds.

      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 run 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 doesn't 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 an fsadm is
      running.

    Options
	   -n new_version      Upgrade disk layout to new_version.
			       new_version can be 3 or 4.

	   -r rawdev	       Use the pathname rawdev as the raw device.
			       This option can be used when vxupgrade cannot
			       determine which raw device corresponds to the
			       mount point (when /etc/mnttab is corrupted,
			       for example).

    Free Space Requirement
      vxupgrade requires free space on the file system to perform the
      upgrade; the upgrade may fail if there is not enough free space.	It
      is difficult to determine the exact amount of space required to
      upgrade a VxFS file system, however, you can estimate the maximum
      space required.





 Hewlett-Packard Company	    - 1 -   HP-UX Release 11i: November 2000






 vxupgrade(1M)						       vxupgrade(1M)




      To upgrade a disk layout Version 2 file system with n * 1024 inodes
      (allocated only) and m * 32768 blocks to disk layout Version 3, the
      worst-case minimum value is at least n * 2432 bytes + m * 8220 bytes +
      115 kilobytes, in extents of 8 kilobytes or larger.  Free extents of
      larger than 8 kilobytes may be required, so this is only a lower bound
      on the worst-case minimum required.  Since this is the worst-case
      minimum, it may be possible to upgrade with less free space available.
      After an upgrade to a new disk layout is completed, all of this free
      space, plus some additional free space, will be reclaimed.

      You cannot upgrade a Version 2 disk layout to Version 4 directly.	 You
      must first upgrade from Version 2 to a Version 3 disk layout, and then
      upgrade to Version 4.  The upgrade may fail due to a lack of space at
      each step.

 NOTES
      Once a file system has been upgraded to Version 3, it is no longer
      mountable on HP-UX 10.01 and 10.10.

      Once a file system has been upgraded to Version 4, it is no longer
      mountable on:

	   +	HP-UX 10.x

	   +	HP-UX 11.0 without JFS 3.3 from Application CD

      Version 4 file systems are mountable on:

	   +	HP-UX 11.0 with JFS 3.3 from Application CD

	   +	HP-UX 11.1x

      You cannot upgrade the root (/) or /usr file systems to Version 4 on
      an 11.0 system running JFS 3.3 from the Application CD.  Additionally,
      we do not advise upgrading the /var or /opt file systems to Version 4
      on an 11.0 system.  These core file systems are crucial for system
      recovery.	 The HP-UX 11.0 kernel and emergency recovery media were
      built with an older version of JFS that does not recognize the Version
      4 disk layout.  If these file systems were upgraded to Version 4, your
      system would fail to boot with the 11.0 kernel as delivered or the
      emergency recovery media.	 You can, however, upgrade these core file
      systems to Version 4 on an HP-UX 11.1x system.

      Disk layout versions cannot be downgraded, for example, you cannot
      change a file system from disk layout version 4 to disk layout version
      3.

      A file system cannot be upgraded from a Version 3 disk layout to a
      Version 4 disk layout if its intent log size is less than 256
      kilobytes.




 Hewlett-Packard Company	    - 2 -   HP-UX Release 11i: November 2000






 vxupgrade(1M)						       vxupgrade(1M)




      After upgrading from a Version 2 disk layout, run fsadm -c mount-point
      to convert the inode format to allow growth beyond a two-gigabyte
      offset.

 DIAGNOSTICS
      vxupgrade returns an exit value of 0 if the upgrade was successful, 1
      if the upgrade failed due to a lack of free space, and 2 if the
      upgrade failed for some other reason.

 FILES
      mount_point/lost+found/.fsadm lock file

 SEE ALSO
      fsadm_vxfs(1M), mkfs_vxfs(1M), vxfsio(7).








































 Hewlett-Packard Company	    - 3 -   HP-UX Release 11i: November 2000