vxupgrade to convert disk layout version

[Rebecca Hounschell]

I upgraded OnLine JFS to 3.3 on an HP9000 N4000 with 11.0 OS approx. 2 months ago. However, I was looking at some old documents and determined that I failed to do the vxupgrade on the disks to convert disk layout from version 3 to version 4. Can I do the vxupgrade at this time without createing any problems? I have not had to use OnLine JFS since I upgraded.

P.S. This thread has been moved from Disk to HP-UX > LVM and VxVM. -HP Forum Moderator

[Iain F. Brown]

There should be no problems upgrading from version 3 to 4 check the man page for vxupgrade for detailed info.
Extract from man page:-

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.