When following the document on how to stop/start a Hyperscale X appliance node
I get to the step unmount the CDS vdisk, and after getting the proper vdisk name and running the cmd
# umount /ws/hedvig/<vdiskname>
i get the message ‘device is busy’.
What’s the proper way to remediate this and continue?
Best answer by GordAView original
Can you check if there are actually no running Commvault processes anymore?
Command: commvault list
Hi, thanks for the reply. Still learning CV and HyperScale X.
Output from commvault list after commvault stop shows
No worries :)
The CvMountd is what's keeping the disk busy.
Can you retry a commvault stop and check if all the services have stopped after the second attempt?
If not logs need to be checked why they aren't stopping.
Let us know ;)
Hi, so in talking to support , the thought was that the services are defunct but the ps -ef | grep defunct doesn’t show any defunct services.
Lazy umount was used to continue the process and reboot the node. After the reboot and restart node, etc the Commserv was able to successfully update the node to 11.28.19
I’ll continue on my other nodes which were also exhibiting the same behaviour of update job failures.
I know sometimes whatever logging would be needed is either long gone, or the debug level was not high enough at the time...
No, we didn’t get that far down the rabbit hole.
You missed out on tea with the Mad Hatter 🤪
Jokes aside, hope this was a one time issue 👍
Yeah I think this issue is behind us now.
I was able to continue using the same lazy umount
umount -l /ws/hedvig
to do the reboots of our other nodes and update to 11.28.19.
Appreciate the confirmation,