So far, we have changed how we mount and unmount the disks. By doing so, we have not had the high CPU usage issue again.
We currently do more checks before mounting the disk. Before we used to mount without checking if the device was actually visible.
we umount the old disk
sudo /sbin/multipath -F
sudo systemctl daemon-reload
sudo /usr/bin/iscsiadm -m session --rescan
sudo /sbin/multipathd reconfigure
sudo /sbin/multipath -ll | grep SCOMPELNTCompellent_Vol. => if exit code is 0 we restart the process with a flush -> reload-> rescan-> reconfigure
otherwise we continue and we check if our device is already visible
sudo /sbin/multipath -ll |grep' , volumeToMount deviceId. => if exit code is 0 we mount it
by following this procedure, we did't had anymore issues with the multipathd/nor CPU usage.
Hi,
So far, we have changed how we mount and unmount the disks. By doing so, we have not had the high CPU usage issue again.
We currently do more checks before mounting the disk. Before we used to mount without checking if the device was actually visible.
we umount the old disk
sudo /sbin/multipath -F
sudo systemctl daemon-reload
sudo /usr/bin/iscsiadm -m session --rescan
sudo /sbin/multipathd reconfigure
sudo /sbin/multipath -ll | grep SCOMPELNTCompel lent_Vol. => if exit code is 0 we restart the process with a flush -> reload-> rescan-> reconfigure
otherwise we continue and we check if our device is already visible
sudo /sbin/multipath -ll |grep' , volumeToMount deviceId. => if exit code is 0 we mount it
by following this procedure, we did't had anymore issues with the multipathd/nor CPU usage.