Problem
An improper umount can lead to nondeterministic behavior, resulting in hangs, filesystem inconsistencies etc. in NetBackup Appliances
Error Message
Note: This is one of the example messages that might appear
During shutdown example:
umount: UX:vxfs umount.vxfs: ERROR: V-3-26299: cannot umount /msdp/data/dp1/pdvol: Device or resource busy
During boot-up example:
mount: UX:vxfs mount.vxfs: ERROR: V-3-20000: Cannot be mounted though fsck has performed log replay.
Cause
Due to improper unmount filesystem has to replay the outstanding transactions which did not reach the disk.
If this replay is interrupted in some ways or if this replay is done on partially written data, the fsck binary can misinterpret the transactions causing this behavior.
Solution
This HotFix adds a new fsck binary that addresses the fsck log replay problems.
This HotFix is available here for NetBackup Appliance 3.1/3.1.1/3.1.2/3.2 releases.
On NetBackup Appliance 3.2, make sure to uninstall this HotFix before installing Maintenance Release 1 and then reinstall this HotFix.
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.