HP-UX HB v13.00 Ch-14 - JFS

HP-UX Handbook – Rev 13.00 Page 34 (of 47)
Chapter 14 Journaled File System (JFS)
October 29, 2013
Message: 026
WARNING: msgcnt x: vxfs: mesg 026: vx_snap_copyblk - mount_point primary file
system read error
Explanation:
Snapshot file system error. When the primary file system is written,copies of the original data
must be written to the snapshot file system. If a read error occurs on a primary file system during
the copy, any snapshot file system that doesn't already have a copy of the data is out of date and
must be disabled.
Action: An error message for the primary file system prints. Resolve the error on the primary
file system and rerun any backups or other applications that were using the snapshot that failed
when the error occurred.
Message: 027
WARNING: msgcnt x: vxfs: mesg 027: vx_snap_bpcopy - mount_point snapshot file
system write error
Explanation:
A write to the snapshot file system failed. As the primary file system is updated, copies of the
original data are read from the primary file system and written to the snapshot file system. If one
of these writes fails, the snapshot file system is disabled.
Action: Check the console log for I/O errors. If the disk has failed, replace it. Resolve the error
on the disk and rerun any backups or other applications that were using the snapshot that failed
when the error occurred.
Message: 028
WARNING: msgcnt x: vxfs: mesg 028: vx_snap_alloc - mount_point snapshot file
system out of space
Explanation:
The snapshot file system ran out of space to store changes. During a snapshot backup, as the
primary file system is modified, the original data is copied to the snapshot file system. This error
can occur if the snapshot file system is left mounted by mistake, if the snapshot file system was
given too little disk space, or the primary file system had an unexpected burst of activity. The
snapshot file system is disabled.
Action: Make sure the snapshot file system was given the correct amount of space. If it was,
determine the activity level on the primary file system. If the primary file system was unusually
busy, rerun the backup. If the primary file system is no busier than normal, move the backup to a
time when the primary file system is relatively idle or increase the amount of disk space
allocated to the snapshot file system. Rerun any backups that failed when the error occurred.