It sounds like you are running on KVM, is that correct?
It also sounds like putting the storage in maintenance mode from CloudStack
does not cause any issues, but stopping the NFS service does cause issues. Is
that correct, as well?
Is it possible the hosts in your compute cluster are putting
when change the C storage to maintance , group normally ,no exception occured.
when stop the NFS on C storage , all vm stoped and some hypervisors rebooted
by cloudstack-agent.
In C storage ,only one file that for VMC1, there aren’t disk image for other
vms , so it stoped all vms to be
Do you know if your other VMs shut down when you stopped the NFS service or
when you put the primary storage into maintenance mode?
Putting a primary storage in maintenance mode should only shut down VMs that
have one or more disks running from that primary storage.
For example, if you had
Our cloudstack (4.9.1) group have 4 primary storage named as A/B/C/D, almost
all vm disk image in A storage. only one vm (name VMC1) disk image in C
storage.
yesterday ,
we close VMC1 and change the C storage to maintance state,
then stop the NFS service in C storage ,
after that ,
