The file systems offline operation gets stuck for more than 2hrs after a reboot all operation

Welcome to Cohesity Documentation.

Ask me anything. From setup and configuration to troubleshooting, architecture, features, and release updates, I'm here to help.

AI may make mistakes. Always verify critical information.

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products

Data Security Alliance

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products

Data Security Alliance

The file systems offline operation gets stuck for more than 2hrs after a reboot all operation — NetBackup Flex Scale 3.0 | Cohesity Documentation

Home

Veritas NetBackup™ Flex Scale Release Notes

Known issues

Miscellaneous issues

The file systems offline operation gets stuck for more than 2hrs after a reboot all operation

Veritas NetBackup™ Flex Scale Release Notes · PDF

Download PDF

After you perform a reboot all operation, the file systems offline operation gets stuck. Hence, few file systems are not available and the respective containers also become offline. The backup/restore operation also get stuck as the primary/media containers are offline or unavailable. (4027460)

Workaround:

Force reboot all the nodes using the echo b > /proc/sysrq-trigger command.

Feedback

Was this page helpful?

Red Hat Virtualization (RHV) VM discovery and backup and restore jobs fail if the Media server node that is selected as the discovery host, backup host, or recovery host is replaced

cvmvoldg agent causes resource faults because the database not updated

Feedback

Was this page helpful?